From 6082c78adb1c9e36c0e2971849a6604229775804 Mon Sep 17 00:00:00 2001 From: Ahmet Alp Balkan Date: Sun, 2 Apr 2023 13:19:12 -0700 Subject: [PATCH] fix: broken link to Node Authorization --- docs/04-certificate-authority.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/04-certificate-authority.md b/docs/04-certificate-authority.md index 1510993..152fe5a 100644 --- a/docs/04-certificate-authority.md +++ b/docs/04-certificate-authority.md @@ -107,7 +107,7 @@ admin.pem ### The Kubelet Client Certificates -Kubernetes uses a [special-purpose authorization mode](https://kubernetes.io/docs/admin/authorization/node/) called Node Authorizer, that specifically authorizes API requests made by [Kubelets](https://kubernetes.io/docs/concepts/overview/components/#kubelet). In order to be authorized by the Node Authorizer, Kubelets must use a credential that identifies them as being in the `system:nodes` group, with a username of `system:node:`. In this section you will create a certificate for each Kubernetes worker node that meets the Node Authorizer requirements. +Kubernetes uses a [special-purpose authorization mode](https://kubernetes.io/docs/reference/access-authn-authz/node/) called Node Authorizer, that specifically authorizes API requests made by [Kubelets](https://kubernetes.io/docs/concepts/overview/components/#kubelet). In order to be authorized by the Node Authorizer, Kubelets must use a credential that identifies them as being in the `system:nodes` group, with a username of `system:node:`. In this section you will create a certificate for each Kubernetes worker node that meets the Node Authorizer requirements. Generate a certificate and private key for each Kubernetes worker node: