Automatic "metadata.name" labels for all Namespaces

[jayunit100]

Enhancement Description

• APIServer defaulted labels for all Namespaces
• Kubernetes Enhancement Proposal: https://github.com/kubernetes/enhancements/tree/master/keps/sig-api-machinery/2161-apiserver-default-labels
• Discussion Link: Network Policy NamespaceSelector Should All Match Against Name kubernetes#88253 (evolved from namespace as name discussions), moved here https://github.com/kubernetes/enhancements/pull/2113/files
• Primary contact (assignee): @jayunit100
• Responsible SIGs: apimachinery, sig-network
• Enhancement target (which target equals to which milestone):
  • Alpha release target (x.y):
  • Beta release target (x.y):
  • Stable release target (x.y):
• Alpha
  • KEP (k/enhancements) update PR(s):
  • Code (k/k) update PR(s):
  • Docs (k/website) update PR(s):

[jayunit100]

/sig apimachinery

[k8s-ci-robot]

@jayunit100: The label(s) sig/apimachinery cannot be applied, because the repository doesn't have them

In response to this:

/sig apimachinery

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.

[jayunit100]

/sig network

[rikatz]

/sig api-machinery

[jayunit100]

https://hackmd.io/Yc9TyoQOQ0e8KgDLK8m2Eg <-- on the kep here w/ @rikatz

[jayunit100]

wait i think this cant be closed until the entire kep is completed, right?

[deads2k]

/milestone v1.21
/stage beta

[annajung]

With PR #2284 merged, this enhancement meets all the criteria for the Enhancements freeze 👍

[arunmk]

Hi @jayunit100,

Since your Enhancement is scheduled to be in 1.21, please keep in mind the important upcoming dates:

• Tuesday, March 9th: Week 9 - Code Freeze
• Tuesday, March 16th: Week 10 - Docs Placeholder PR deadline
  • If this enhancement requires new docs or modification to existing docs, please follow the steps in the Open a placeholder PR doc to open a PR against k/website repo.

As a reminder, please link all of your k/k PR(s) and k/website PR(s) to this issue so we can track them.

Thanks!

[arunmk]

Hi @jayunit100,

Enhancements team does not have a linked PR to track for the upcoming code freeze. Could you please link a PR to this KEP so that we may track it.

We are currently marking this KEP as 'At Risk' for the upcoming code freeze on 3/9.

Thanks

[arunmk]

Hi @jayunit100,

A friendly reminder that Code freeze is 4 days away, March 9th EOD PST

Any enhancements that are NOT code complete by the freeze will be removed from the milestone and will require an exception to be added back.

Please also keep in mind that if this enhancement requires new docs or modification to existing docs, you'll need to follow the steps in the Open a placeholder PR doc to open a PR against k/website repo by March 16th EOD PST

Thanks!

[annajung]

Hi @jayunit100, with kubernetes/kubernetes#96968 merged, we will mark this as code complete for the upcoming code freeze.

[PI-Victor]

Hello @jayunit100, 1.21 Docs shadow here.
Does this enhancement work planned for 1.21 require any new docs or modification to existing docs?
If so, please follows the steps here to open a PR against dev-1.21 branch in the k/website repo. This PR can be just a placeholder at this time and must be created by March 16 EOD PST
Also take a look at Documenting for a release to get yourself familiarize with the docs requirement for the release.
Thank you!

[rikatz]

Hi @PI-Victor :)

I've added the missing docs.

Thanks!

[JamesLaverack]

Hey @jayunit100, 1.22 Enhancements Lead here.

Just a couple of questions about this enhancement ahead of enhancements freeze:

• What is your graduation criteria for stable? Your KEP only mentions "This feature being enabled by default at least one release." was that for beta? What specificly needs to be permitted for stable?
• We require an approved production readiness review, but I don't see one at the stable stage. Have you reached out to the PRR team about this graduation?
• You have SIG Network listed as an associated SIG. Do SIG Network need to do anything for this graduation, and if so are they signed on to doing that in 1.22?

Please let me know if you have any questions.

[JamesLaverack]

With #2736 and #2651 merged, this enhancement is complete for enhancements freeze.

@jayunit100 Can you clarify if SIG Network need to do anything?

[chrisnegus]

Hi @jayunit100 ! I'm @chrisnegus , a Docs Shadow for release 1.22.
This enhancement is marked as Needs Docs for the 1.22 release.

Please follow the steps detailed in the documentation to open a PR against dev-1.22 branch in the kubernetes/website repo. This PR can be just a placeholder at this time and must be created before Fri July 9, 11:59 PM PDT.

Also, take a look at Documenting for a release to familiarize yourself with the docs requirement for the release.

Thank you!

[JamesLaverack]

Hey @jayunit100, can you confirm if kubernetes/kubernetes#101342 is the only k/k PR required for this enhancement in 1.22?

[JamesLaverack]

Hey again @jayunit100. Can I quickly ask you to confirm if kubernetes/kubernetes#101342 is the only k/k PR required for this enhancement in v1.22? If it isn't then as a reminder the deadline for code freeze is in five days on Thursday 8th July at 18:00 PDT.

As an additional reminder, the docs placeholder PR deadline is the day after code freeze on Friday 9th July.

[rikatz]

@JamesLaverack Jay is on PTO this week, but I can confirm this is the only required PR to make this GA.

Next step is to remove at all the featuregate and the codes containing the FG, probably in next release :)

[JamesLaverack]

Great, thank you for confirming @rikatz. I believe this enhancement is all good to go for v1.22 code freeze. :)

[PI-Victor]

Hi @jayunit100 ! I'm @chrisnegus , a Docs Shadow for release 1.22.
This enhancement is marked as Needs Docs for the 1.22 release.

Please follow the steps detailed in the documentation to open a PR against dev-1.22 branch in the kubernetes/website repo. This PR can be just a placeholder at this time and must be created before Fri July 9, 11:59 PM PDT.

Also, take a look at Documenting for a release to familiarize yourself with the docs requirement for the release.

Thank you!

@rikatz hello again, friendly reminder about the upcoming docs placeholder PR Fri July 9, 11:59 PM PDT, thanks!

[PI-Victor]

@rikatz Today is docs placeholder deadline, please submit a placeholder PR by the end of the day, today!

[rikatz]

Hey @PI-Victor

was looking at this yesterday and figured out someone already updated the feature gate docs and the other docs are correct, so this one is Ok and no new doc is necessary :)

[salaxander]

@jayunit100 @rikatz - With the KEP status marked as implemented, I'm going to close out this issue. Great job everyone!

[thockin]

Reminder: Remove gate in 1.25, milestone updated