-
Notifications
You must be signed in to change notification settings - Fork 1.5k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Standard Topology Labels #1659
Comments
Hi @thockin ! 1.19 Enhancements shadow here. I wanted to check in and see if you think this Enhancement will be graduating in 1.19? In order to have this part of the release: The KEP PR must be merged in an implementable state The current release schedule is: Monday, April 13: Week 1 - Release cycle begins Please let me know and I'll add it to the 1.19 tracking sheet (http://bit.ly/k8s-1-19-enhancements). Once coding begins please list all relevant k/k PRs in this issue so they can be tracked properly. 👍 Thanks! |
Hi @thockin ! Gentle reminder: Enhancements Freeze is Tuesday, May 19th (EOD PST). To be included in the release, this enhancement must have a merged KEP in the implementable status. The KEP must also have graduation criteria and a Test Plan defined. Once coding begins please list all relevant k/k PRs in this issue so they can be tracked properly. As an additional note, #1620 merged recently, adding production readiness review questions to the KEP template. We are not making it mandatory for the 1.19 release cycle, but it would be great if the PRR questionnaire is filled since the KEP PR is in flight. If you have any questions please let me know. Thanks! |
As a reminder, enhancements freeze is tomorrow May 19th EOD PST. In order to be included in 1.19 all KEPS must be implementable with graduation criteria and a test plan. Thanks. |
Unfortunately the deadline for the 1.19 Enhancement freeze has passed. For now this is being removed from the milestone and 1.19 tracking sheet. If there is a need to get this in, please file an enhancement exception. |
Issues go stale after 90d of inactivity. If this issue is safe to close now please do so with Send feedback to sig-testing, kubernetes/test-infra and/or fejta. |
/remove-lifecycle stale |
Hi @thockin Enhancements Lead here. Any plans for this in 1.20? |
Circling back around on this, any plans for 1.20? I see that the KEP is still provisional, since it's docs, it doesn't need test plan/graduation. Please let me know your plans so we can track this - a reminder Enhancements Freeze is October 6th. Best, |
Define standard topology labels
topology.kubernetes.io/region
andtopology.kubernetes.io/zone
are standard and are safe to build topology-based features aroundThe text was updated successfully, but these errors were encountered: