From 66350ad1f24361ab9f8bc484787c271f82ab8f8d Mon Sep 17 00:00:00 2001 From: Sam Clinckspoor Date: Tue, 21 Nov 2017 14:17:32 +0100 Subject: [PATCH] Fix links to Node auth and NodeRestrictions --- docs/admin/authorization/rbac.md | 4 +--- 1 file changed, 1 insertion(+), 3 deletions(-) diff --git a/docs/admin/authorization/rbac.md b/docs/admin/authorization/rbac.md index 85963009cf..f387f44456 100644 --- a/docs/admin/authorization/rbac.md +++ b/docs/admin/authorization/rbac.md @@ -463,9 +463,7 @@ The permissions required by individual control loops are contained in the system:node None in 1.8+ Allows access to resources required by the kubelet component, including read access to all secrets, and write access to all pod status objects. -As of 1.7, use of the [Node authorizer](/docs/admin/authorization/node/) -and [NodeRestriction admission plugin](/docs/admin/admission-controllers#NodeRestriction) -is recommended instead of this role, and allow granting API access to kubelets based on the pods scheduled to run on them. +As of 1.7, use of the Node authorizer and NodeRestriction admission plugin is recommended instead of this role, and allow granting API access to kubelets based on the pods scheduled to run on them. Prior to 1.7, this role was automatically bound to the `system:nodes` group. In 1.7, this role was automatically bound to the `system:nodes` group if the `Node` authorization mode is not enabled. In 1.8+, no binding is automatically created.