Skip to content

Commit 4d051d9

Browse files
authored
Fix well-known label name
1 parent 648cda5 commit 4d051d9

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

content/en/docs/concepts/scheduling-eviction/topology-spread-constraints.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -253,7 +253,7 @@ confusing and troubleshooting is less straightforward.
253253
You need a mechanism to ensure that all the nodes in a topology domain (such as a
254254
cloud provider region) are labelled consistently.
255255
To avoid you needing to manually label nodes, most clusters automatically
256-
populate well-known labels such as `topology.kubernetes.io/hostname`. Check whether
256+
populate well-known labels such as `kubernetes.io/hostname`. Check whether
257257
your cluster supports this.
258258

259259
## Topology spread constraint examples

0 commit comments

Comments
 (0)