/sig scheduling

@vllry I'm going to add this to the 1.15 milestone for tracking purposes. Please link to any k/k PRs so we can see the status of the merges to make sure this will make it to code freeze.

/milestone v1.15
/stage alpha

/assign @denkensk

Hey, @denkensk @vllry Is alpha release of this enhancement targeted for v1.15?

@daminisatya it is, but I believe API review is still pending.

Thank you @vllry

Just a friendly reminder we're looking for a PR against k/website (branch dev-1.15) due by Thursday, May 30th. It would be great if it's the start of the full documentation, but even a placeholder PR is acceptable. Let me know if you have any questions! 😄

@denkensk do you have time to start docs, or would you like me to start?

@denkensk do you have time to start docs, or would you like me to start?

@vllry Thank you. You can help to start docs If you have time.

Placeholder docs PR is up: kubernetes/website#14599

@daminisatya what's the deadline for merging the documentation?

Hi, @vllry documentation should be merged by 10th June. but the deadline is broken down to

• 30th deadline for placeholder PR
• 04th deadline for all placeholder to have reviewable content
• 10th all docs PR should be merged.

Thanks.

@vllry @denkensk, today is code freeze for the 1.15 release cycle. The k/k PRs have not yet been merged. It's now being marked as At Risk in the 1.15 Enhancement Tracking Sheet.

Is there a high confidence these will be merged by EOD PST today? After this point, only release-blocking issues and PRs will be allowed in the milestone with an exception.

/milestone clear

@kacole2 why was this removed from 1.15? The PR was merged last night.

@vllry I apologize about that! I didn't see the PR listed in the original post. adding it back!

/milestone v1.15

Sorry about the lack of clarity! Doc PR is open and being refined, let me know if anything is missing.

I apologize about that! I didn't see the PR listed in the original post. adding it back!

I reference this merged pr here kubernetes/kubernetes#74614 thank you

GA Progress Record：

• k/enhancements: Graduate NonPreemptingPriority to GA #3110
• k/k Add details about preemption in the event for scheduling failed kubernetes#107775 Graduate NonPreemptingPriority to GA kubernetes#107432
• k/website: Graduate NonPreemptingPriority to GA website#31283

/milestone v1.24

Hello @denkensk 👋, 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.

With all the KEP requirements in place & merged into k/enhancements, this enhancement is all good for the upcoming enhancements freeze. 🚀

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

GA Progress Record：

• k/enhancements: Graduate NonPreemptingPriority to GA #3110
• k/k Add details about preemption in the event for scheduling failed kubernetes#107775 Graduate NonPreemptingPriority to GA kubernetes#107432
• k/website: Graduate NonPreemptingPriority to GA website#31283

All pr for GA have been merged.

Hello @denkensk 👋

With 1.24 Code Freeze approaching on 18:00 PDT Tuesday March 29th 2022, I'm just checking in once more.

• All PRs to the Kubernetes repo that are related to your enhancement are merged by the code freeze deadline.
  • Add details about preemption in the event for scheduling failed kubernetes#107775
  • Graduate NonPreemptingPriority to GA kubernetes#107432
• Have a documentation placeholder PR open by Thursday, March 31, 2022.
  • Graduate NonPreemptingPriority to GA website#31283

With all the required KEP PRs merged into k/enhancements & k/website, this enhancement is all good for the upcoming 1.24 code freeze. 🚀 For note, the status of this enhancement is marked as tracked.

Kindly please let me know if I'm missing any PRs other than the ones I linked above.

Also please link all the milestone PRs in the above issue description (for tracking purposes). Thank you so much!

Hello @denkensk, could you please confirm is the following PR is part of the GA implementation for the enhancement? Thanks!

• support preemptionPolicy in describe PriorityClass kubernetes#108701

Hello @denkensk, could you please confirm is the following PR is part of the GA implementation for the enhancement? Thanks!

• support preemptionPolicy in describe PriorityClass kubernetes#108701

Hi @Priyankasaggu11929 It's not the necessary part of GA.

Thanks so much for the prompt confirmation, @denkensk!

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

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

Graduated to GA