Hi @wojtek-t

Enhancements Lead here. Updated the description above to link directly to the merged KEP, updated tracking sheet and tags to reflect alpha in 1.20.

Let me know if you need anything or if anything changes.

Thanks,
Kirsten

@kikisdeliveryservice - yes, I'm targetting Alpha in 1.20

Thanks for already adding tags!

Hi @wojtek-t ,

Since your Enhancement is scheduled to be in 1.20, please keep in mind the important upcoming dates:
Friday, Nov 6th: Week 8 - Docs Placeholder PR deadline
Thursday, Nov 12th: Week 9 - Code Freeze

As a reminder, please link all of your k/k PR as well as docs PR to this issue so we can track them.

Regards,
Jeremy

Hello @wojtek-t , 1.20 Docs shadow here.

Does this enhancement work planned for 1.20 require any new docs or modification to existing docs?

If so, please follows the steps here to open a PR against the dev-1.20 branch in the k/website repo. This PR can be just a placeholder at this time and must be created before Nov 6th.

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

Thank you!

@reylejano-rxm - we don't need any documents for it.

Hi @wojtek-t

Please keep in mind the important upcoming dates:

• Friday, Nov 6th: Week 8 - Docs Placeholder PR deadline Docs Not Required
• Thursday, Nov 12th: Week 9 - Code Freeze
• Monday, Nov 23rd: Week 11 - Docs PR Ready for Review Docs Not Required

As a reminder, please link all of your k/k PR as well as docs PR to this issue for the release team to track.

We're fine - it's Alpha-ready.

/milestone v1.21

I'm assuming we want to go beta in 1.21?

Thanks Daniel - yes, that's my plan.
I will try to send a KEP update for beta later this week.

Send out #2267 for review

/remove-lifecycle stale

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

/remove-lifecycle stale

Hello @wojtek-t 👋, 1.24 Enhancements team here.

Just checking in as we approach enhancements freeze on 18:00pm PT on Thursday Feb 3rd, 2022.
For note, This enhancement is targeting for stage stable for 1.24, (correct me if otherwise)

Here’s where this enhancement currently stands:

• Updated KEP file using the latest template has been merged into the k/enhancements repo.
• KEP status is marked as implementable for this release
• KEP has a test plan section filled out.
• KEP has up to date graduation criteria.
• KEP has a production readiness review that has been completed and merged into k/enhancements.

Looks like, the enhancement is good for the upcoming enhancements freeze. 🚀

The status of this enhancement is marked as Tracked. Please update this issue description with appropriate stages as well. Thank you!

Updated issue description - other than that it sounds fine.

Hi @wojtek-t 👋🏻 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!

@mehabhalodiya - this was marked by mistake - this doesn't require docs. Can you please update the update the spreadsheet that it's not needed?

@wojtek-t We had a discussion for Need Docs or No Docs required over Slack for this enhancement.

@sftim suggested:

we'd need an update to https://kubernetes.io/docs/reference/command-line-tools-reference/feature-gates/ to record that the feature is now GA, so I think we do need a docs change.

Also, @PI-Victor agreed with Tim, saying:

if the feature is now moved to GA, in the features list gates table md file, all the information regarding that feature gate should be moved down into the table below (Feature gates for graduated or deprecated features). https://github.com/kubernetes/website/blob/main/content/en/docs/reference/command-line-tools-reference/feature-gates.md
e.g.: https://github.com/kubernetes/website/pull/31283/files

Thus, considering the above pointers we are moving this enhancement to Needs Docs status.
Please follow this comment.
Thank you 🙂

I opened kubernetes/website#31770 for docs change.

Hi @wojtek-t

I'm checking in as we approach 1.24 code freeze at 01:00 UTC Wednesday 30th March 2022.

Please ensure the following items are completed:

• All PRs to the Kubernetes repo that are related to your enhancement are linked in the above issue description (for tracking purposes).
• All PRs are fully merged by the code freeze deadline.

For this KEP, it looks like all k/k PRs have been merged. Are there any other PRs that you think we should be tracking that would be subject to the 1.24 code freeze?

Let me know if you have any questions.

@rhockenbury - everything is done - it's good to go.

Hello @wojtek-t 👋, 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! 🙂