You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: content/en/docs/concepts/architecture/nodes.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -143,7 +143,7 @@ For example, you can set labels on an existing Node or mark it unschedulable.
143
143
You can set optional node role(s) for nodes by adding one or more `node-role.kubernetes.io/<role>: <role>` labels to the node where characters of `<role>`
144
144
are limited by the [syntax](/docs/concepts/overview/working-with-objects/labels/#syntax-and-character-set) rules for labels.
145
145
146
-
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.
146
+
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.
147
147
148
148
You can use labels on Nodes in conjunction with node selectors on Pods to control
149
149
scheduling. For example, you can constrain a Pod to only be eligible to run on
0 commit comments