Code change:
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: The docs for  say that this label is set on namespaces when you enable a feature gate, . However that's no longer true. In current Kubernetes the control plane always sets that label on namespaces. Proposed Solution: Reword that section to make it clear that the control plane always sets that label Page to Update: Kubernetes Version: v1.22 Additional Information: /language en /kind bug /help /priority backlog
This request has been marked as needing help from a contributor. Please ensure that the issue body includes answers to the following questions: Why are we solving this issue? To address this issue, are there any code changes? If there are code changes, what needs to be done in the code and what places can the assignee treat as reference points? Does this issue have zero to low barrier of entry? How can the assignee reach out to you for help? For more details on the requirements of such an issue, please see and ensure that they are met. If this request no longer meets these requirements, the label can be removed by commenting with the command. <detailsIn response to : This is a Bug Report <!-- See for guidance on writing an actionable issue description. --Problem: The docs for  say that this label is set on namespaces when you enable a feature gate, . However that's no longer true. In current Kubernetes the control plane always sets that label on namespaces. Reword that section to make it clear that the control plane always sets that label Kubernetes Version: v1.22 /language en /kind bug /help /priority backlog </details
/triage accepted
Hi, I would like to work on this issue. /assign
Any questions about how to fix it?
I have a few technical questions: the sets the label on the namespaces instead of enabling the , so there would be no role of K8s API server in this process? will the set label on the namespaces? I mean will it do it automatically or we need to do something to set the labels like enabling something?
The API server is part of the control plane - see The component within the control plane that sets the label isn't a detail we need to specify here. All we need to mention is that it happens, and phrase it to make it clear it's not optional.
Just to be clear that the will set the labels of the namespace and this setting of the labels is compulsorily (i.e. it is not optional).?
(also, we'll get the API Machinery folks to check technical accuracy anyway - it's not on the docs contributors to thoroughly verify this kind of detail).
Okay thanks . I now have an idea on how to fix the issue, I will file the PR soon :)
I have a doubt: The phrase which tells that ,would it be better to included it as a shortcode or it should be kept as a normal text.?
the best way for folks to review your proposed changes is to open a pull request. (Also: anyone else who wants to work on this is welcome to - please liaise with if that's feasible).
I have filed a PR but if anyone wants to work on this they are welcome to share their suggestions in the PR Conversation. Thanks.

Related discussion:
text: Used on: Namespaces <del> When the `NamespaceDefaultLabelName` [feature gate](/docs/reference/command-line-tools-reference/feature-gates/) is enabled, the Kubernetes API server sets this label on all namespaces. The label value is set to the name of the namespace. </del> <ins> The Kubernetes API server (part of the {{< glossary_tooltip text="control plane" term_id="control-plane" >}}) sets this label on all namespaces. The label value is set to the name of the namespace. You can't change this label's value. </ins> This is useful if you want to target a specific namespace with a label {{< glossary_tooltip text="selector" term_id="selector" >}}.