From ec935a9f35d187ca12a03038d52758432d352808 Mon Sep 17 00:00:00 2001 From: adriancuadrado Date: Sun, 24 Dec 2023 00:38:40 +0100 Subject: [PATCH] Fixed broken link at 04-certificate-authority.md --- 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: