From dca907142c10b718c4c6d6f7b032f5929c02166c Mon Sep 17 00:00:00 2001 From: Aaina26 Date: Thu, 30 Jan 2025 15:25:00 +0530 Subject: [PATCH] fixed slight error in a sentence --- 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 6f7d17576f..7f245e7ce8 100644 --- a/content/en/docs/concepts/architecture/nodes.md +++ b/content/en/docs/concepts/architecture/nodes.md @@ -143,7 +143,7 @@ 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](/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. +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 the label key. You can use labels on Nodes in conjunction with node selectors on Pods to control scheduling. For example, you can constrain a Pod to only be eligible to run on