Change:
The control plane adds this label to an Endpoints object when the owning Service is headless. <ins> ### service.kubernetes.io/topology-aware-hints (deprecated) {#servicekubernetesiotopology-aware-hints} Example: `service.kubernetes.io/topology-aware-hints: "Auto"` Used on: Service This annotation was used for enabling _topology aware hints_ on Services. Topology aware hints have since been renamed: the concept is now called [topology aware routing](/docs/concepts/services-networking/topology-aware-routing/). Setting the annotation to `Auto`, on a Service, configured the Kubernetes control plane to add topology hints on EndpointSlices associated with that Service. You can also explicitly set the annotation to `Disabled`. If you are running a version of Kubernetes older than {{< skew currentVersion >}}, check the documentation for that Kubernetes version to see how topology aware routing works in that release. There are no other valid values for this annotation. If you don't want topology aware hints for a Service, don't add this annotation. </ins> ### kubernetes.io/service-name {#kubernetesioservice-name} Type: Label

Discussion:
This is a Bug Report <!-- Thanks for filing an issue! Before submitting, please fill in the following information. --<!-- See for guidance on writing an actionable issue description. --<!--Required Information--Problem: doesn't list the annotation . Proposed Solution: Add to the Well-Known Labels, Annotations and Taints reference. Page to Update: <!--Optional Information (remove the comment tags around information you would like to include)--<!--Kubernetes Version:--Additional Information: See for details, and maybe put a link in the annotation reference that links there. /language en /sig network
We should fix this before graduates to stable.
/assign
Anyone is welcome to contribute.
/triage accepted
The Kubernetes project currently lacks enough contributors to adequately respond to all issues and PRs. This bot triages issues and PRs according to the following rules: After 90d of inactivity, is applied After 30d of inactivity since was applied, is applied After 30d of inactivity since was applied, the issue is closed You can: Mark this issue or PR as fresh with Mark this issue or PR as rotten with Close this issue or PR with Offer to help out with [Issue Triage][1] Please send feedback to sig-contributor-experience at . /lifecycle stale [1]:
It looks like we resolved it in /close
Closing this issue. <detailsIn response to : It looks like we resolved it in Instructions for interacting with me using PR comments are available . If you have questions or suggestions related to my behavior, please file an issue against the repository. </details
still doesn't list the annotation . /reopen
Reopened this issue. <detailsIn response to : still doesn't list the annotation . Instructions for interacting with me using PR comments are available . If you have questions or suggestions related to my behavior, please file an issue against the repository. </details
The Kubernetes project currently lacks enough active contributors to adequately respond to all issues and PRs.

This bot triages issues and PRs according to the following rules: After 90d of inactivity, is applied After 30d of inactivity since was applied, is applied After 30d of inactivity since was applied, the issue is closed You can: Mark this issue or PR as fresh with Close this issue or PR with Offer to help out with [Issue Triage][1] Please send feedback to sig-contributor-experience at . /lifecycle rotten [1]:
Thanks! I'd really missed that I didn't add it to this page. Will create PR with the fix today /assign
/remove-lifecycle rotten
/lifecycle frozen