From df6a3fbd1e52887e4789ffa07016bbca87bc9b3f Mon Sep 17 00:00:00 2001 From: Aaina26 Date: Sun, 26 Jan 2025 21:52:47 +0530 Subject: [PATCH] slight change in link --- content/en/docs/concepts/architecture/nodes.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/content/en/docs/concepts/architecture/nodes.md b/content/en/docs/concepts/architecture/nodes.md index aafc9127cc..6f7d17576f 100644 --- a/content/en/docs/concepts/architecture/nodes.md +++ b/content/en/docs/concepts/architecture/nodes.md @@ -141,7 +141,7 @@ You can modify Node objects regardless of the setting of `--register-node`. For example, you can set labels on an existing Node or mark it unschedulable. You can set optional node role(s) for nodes by adding one or more `node-role.kubernetes.io/: ` labels to the node where characters of `` -are limited by the [syntax](https://kubernetes.io/docs/concepts/overview/working-with-objects/labels/#syntax-and-character-set) rules for labels. +are limited by the [syntax](/docs/concepts/overview/working-with-objects/labels/#syntax-and-character-set) rules for labels. Kubernetes ignores the label value for node roles;by convention, you can set it to the same string you used for the node role in label key.