[ko] Incorrect topology label in "Pod Topology Spread Constraints" page

[omkensey]

In the English version of the above page, the last paragraph of the Consistency section reads:

You need a mechanism to ensure that all the nodes in a topology domain (such as a cloud provider region) are labelled consistently. To avoid you needing to manually label nodes, most clusters automatically populate well-known labels such as kubernetes.io/hostname. Check whether your cluster supports this.

But in the Korean page's version of that paragraph, the label used as an example is topology.kubernetes.io/hostname which is incorrect.

[k8s-ci-robot]

This issue is currently awaiting triage.

SIG Docs takes a lead on issue triage for this website, but any Kubernetes member can accept issues by applying the triage/accepted label.

The triage/accepted label can be added by org members by writing /triage accepted in a comment.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

[dipesh-rawat]

Page mentioned in issue: https://kubernetes.io/ko/docs/concepts/scheduling-eviction/topology-spread-constraints/
/language ko

[dipesh-rawat]

/retitle [ko] Incorrect topology label in "Pod Topology Spread Constraints" page
/kind bug

[jihoon-seo]

@omkensey Thanks for raising this issue.
The outdatedness of that page has been reported in the issue #41613,
and updated to the dev-1.27-ko.1 branch via the PR #41825. (Fixed line)
When the dev-1.27-ko.1 branch gets merged into main in the future, we will be able to check the updated contents.

Considering the aspects above, let me close this issue.
Again, thank you for your contribution!

/triage duplicate
/close

[k8s-ci-robot]

@jihoon-seo: Closing this issue.

In response to this:

@omkensey Thanks for raising this issue.
The outdatedness of that page has been reported in the issue #41613,
and updated to the dev-1.27-ko.1 branch via the PR #41825. (Fixed line)
When the dev-1.27-ko.1 branch gets merged into main in the future, we will be able to check the updated contents.

Considering the aspects above, let me close this issue.
Again, thank you for your contribution!

/triage duplicate
/close

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.