From 55daf89047837c0684e2ce5cd20068cb3807f6f6 Mon Sep 17 00:00:00 2001 From: Derek Nola Date: Thu, 17 Oct 2024 10:38:22 -0700 Subject: [PATCH] SImplify k8s KEP link Signed-off-by: Derek Nola --- docs/advanced.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/advanced.md b/docs/advanced.md index b6f099d9c..e1db13769 100644 --- a/docs/advanced.md +++ b/docs/advanced.md @@ -279,7 +279,7 @@ All current versions of Kubernetes restrict nodes from registering with most lab > Nodes are not permitted to assert their own role labels. Node roles are typically used to identify privileged or control plane types of nodes, and allowing nodes to label themselves into that pool allows a compromised node to trivially attract workloads (like control plane daemonsets) that confer access to higher privilege credentials. -See [SIG-Auth KEP 279](https://github.com/kubernetes/enhancements/blob/master/keps/sig-auth/279-limit-node-access/README.md#proposal) for more information. +See [SIG-Auth KEP 279](https://github.com/kubernetes/enhancements/blob/master/keps/sig-auth/279-limit-node-access/README.md) for more information. If you want to change node labels and taints after node registration, or add reserved labels, you should use `kubectl`. Refer to the official Kubernetes documentation for details on how to add [taints](https://kubernetes.io/docs/concepts/configuration/taint-and-toleration/) and [node labels.](https://kubernetes.io/docs/tasks/configure-pod-container/assign-pods-nodes/#add-a-label-to-a-node)