hi @adtac I am one of the enhancement shadows for 1.21 and am reviewing this feature. I did not find graduation criteria for alpha phase in the kep. Could you please let me know if there are any?

We don't have any criteria for alpha -- the feature will be turned off by default and we expect users to test it for the first time in alpha. Feedback from users will be a part of beta graduation, but the criteria for alpha is pretty much just the existence of the KEP.

Hi @adtac

This KEP looks good and I don't see any thing missing. However I am adding this message for the sake of completeness.

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

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

[DONE] The KEP must be merged in an implementable state
[DONE] The KEP must have test plans: needs to be updated in the right section as per template
[DONE] The KEP must have graduation criteria
[DONE] The KEP must have a production readiness review

Hi @adtac,

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!

Hi @adtac ,

Enhancements team is currently tracking the following PR

• batch API: add suspended job kubernetes#98727

I went through the review comments and there are a few comments requiring some amount of work. However since this is the only PR in this KEP, I am leaning towards keeping the status as Tracked rather than At Risk. However please note that the code freeze is on 3/9.

Thanks

Hi @adtac,

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!

Hi @adtac, since the only PR mentioned earlier has been merged, can this KEP be marked as done?

@arunmk yes, the implementation is complete. Note that the docs PR is still open and under review.

/assign @adtac

/milestone v1.22

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

We can probably graduate to GA in 1.24

/milestone v1.24

Hello @adtac 👋, 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
  • (the feature is already implemented & moving to stable)
• KEP has a test plan section filled out.
• KEP has up to date graduation criteria.
• KEP has a production readiness review for stage stable that has been completed and merged into k/enhancements.

With all the boxes checked, this enhancement is ready for the upcoming 1.24 enhancements freeze. 🚀

For note, at the moment, the status of this enhancement is marked as tracked. Please keep the issue description up-to-date with appropriate stages as well. Thank you!

Hi, KEP for stable graduation is already merged: #3115

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

Hello @ahg-g 👋

I'm just checking in once more as we approach the 1.24 Code Freeze on 18:00 PDT, Tuesday, March 29th 2022

Please ensure the following items are completed:

• All PRs to the Kubernetes repo that are related to your enhancement are merged by the code freeze deadline.
  • Graduate SuspendJob to GA kubernetes#108129
• Have a documentation placeholder PR open by 18:00 PDT, Thursday, March 31, 2022.

For note, the status of this enhancement is currently marked as at risk.

Kindly please let me know if I'm missing any open PRs other than the ones I linked above. Thank you so much!

Docs PR: kubernetes/website#32350

@ahg-g, thank you so much.

With the Docs PR open now, all requirements for Code Freeze are finished. The status is now tracked.

Hello @ahg-g 👋, 1.25 Enhancements team here.

Since this feature has been fully implemented and is now GA in K8s version v1.24 🎉 (which is also properly updated as implemeted in the status of the kep.yaml file).

I'm closing this issue for the purpose of accurate tracking for v1.25. Thank you so much for your valuable contributions. 🙏 🙂

/close

@Priyankasaggu11929: Closing this issue.