kubernetes
/
website
mirror of https://github.com/kubernetes/website.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

Fix well-known label name

This commit is contained in:
Ruslan Stelmachenko 2023-04-28 21:27:29 +02:00 committed by GitHub
parent 648cda5113
commit 4d051d9b29
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 1 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

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

@ -253,7 +253,7 @@ confusing and troubleshooting is less straightforward.
You need a mechanism to ensure that all the nodes in a topology domain (such as a You need a mechanism to ensure that all the nodes in a topology domain (such as a
cloud provider region) are labelled consistently. cloud provider region) are labelled consistently.
To avoid you needing to manually label nodes, most clusters automatically To avoid you needing to manually label nodes, most clusters automatically
populate well-known labels such as `topology.kubernetes.io/hostname`. Check whether populate well-known labels such as `kubernetes.io/hostname`. Check whether
your cluster supports this. your cluster supports this.
## Topology spread constraint examples ## Topology spread constraint examples