/sig cloud-provider

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

/sig network

Hi @andrewsykim

Enhancements Lead here. Can you confirm that this is for stable in 1.20? As a note, there also doesn't seem to be a KEP attached.

Thanks
Kirsten

Hi @andrewsykim

Any updates on this for 1.20? There is no KEP on this issue.

Enhancements Freeze is October 6th and by that time we require:

The KEP must be merged in an implementable state
The KEP must have test plans
The KEP must have graduation criteria
The KEP must have an issue in the milestone

Best,
Kirsten

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle stale

/remove-lifecycle stale

Hi @andrewsykim, 1.21 Enhancements Lead here

For the enhancement to be included in the milestone, it must meet the following criteria:

• [DONE] The KEP must be merged in an implementable state
• [DONE] The KEP must have test plans
• [DONE] The KEP must have graduation criteria
• The KEP must have a production readiness review

Starting 1.21, all KEP must include a production readiness review. Please make sure to take a look at the instructions and update the KEP to include this and a file under https://github.com/kubernetes/enhancements/tree/master/keps/prod-readiness/sig-network.

Thank you!

Hi @andrewsykim

Enhancements Freeze is 2 days away, Feb 9th EOD PST

Enhancements team is NOT tracking any open PR for a KEP update. Please make sure to work on missing requirements and get it merged before the freeze. For PRR related questions or to boost the PR for PRR review, please reach out in slack #prod-readiness

Any enhancements that do not complete the KEP requirements by the freeze will require an exception.

PRR update #2442

With PR #2442 merged in, this enhancement has met all the criteria for the enhancements freeze 👍

Hi @andrewsykim

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!

/assign

Hi @andrewsykim

Enhancements team is marking this enhancement as "At Risk" for the upcoming code freeze due to not seeing any linked k/k PR(s) for this enhancement.

Please make sure to provide all k/k PR(s) and k/website PR(s) to this issue so it can be tracked by the release team.

Hello, @andrewsykim, just saw that this enhancement is expected to be included in the 1.24 release.

Could you please submit the enhancement issue into the 1.24 tracking sheet so the enhancements team can keep track of it?
Thank you so much!

All good for 1.24 Enhancements Freeze

Hi @andrewsykim 👋 1.24 Docs shadow here.

This enhancement is marked as 'Needs Docs' for the 1.24 release.

Please follow the steps detailed in the documentation to open a PR against the dev-1.24 branch in the k/website repo. This PR can be just a placeholder at this time and must be created before Thu March 31, 11:59 PM PDT.

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

Thanks!

^ @XudongLiuHarold

Thanks @andrewsykim ! hi @chrisnegus , I will take care of it from here😄.

Thanks @XudongLiuHarold !

draft PR for k/website repo: kubernetes/website#31815

Thanks for filing the docs PR @XudongLiuHarold !

Hi @andrewsykim 1.24 Enhancements Team here,

With Code Freeze approaching on 18:00 PDT Tuesday March 29th 2022, the enhancement status is at risk as there is no linked k/k PR. Kindly list them in this issue. Thanks!

PR is here kubernetes/kubernetes#107979, thanks

Hi @andrewsykim 👋 1.24 Release Comms team here.

We have an opt-in process for the feature blog delivery. If you would like to publish a feature blog for this issue in this cycle, then please opt in on this tracking sheet.

The deadline for submissions and the feature blog freeze is scheduled for 01:00 UTC Wednesday 23rd March 2022 / 18:00 PDT Tuesday 22nd March 2022. Other important dates for delivery and review are listed here: https://github.com/kubernetes/sig-release/tree/master/releases/release-1.24#timeline.

For reference, here is the blog for 1.23.

Please feel free to reach out any time to me or on the #release-comms channel with questions or comments.

Thanks!

Marking this as tracked for Code Freeze 🥳

Hello @andrewsykim 👋, 1.25 Enhancements team here.

This feature has been fully implemented and is now GA in K8s version 1.24. 🎉

Please update the kep.yaml file's status to implemented and close this issue.

This would help accurate tracking in the v1.25 cycle. Thank you so much! 🙂

TODO: remove the gate in 1.26

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, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue or PR as fresh with /remove-lifecycle stale
• Mark this issue or PR as rotten with /lifecycle rotten
• Close this issue or PR with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

Since the gate is to be removed in 1.26 keeping this issue open until then

/remove-lifecycle stale

PR to remove the feature gate: kubernetes/kubernetes#112577

Complete!