Pod Priority Based Node Graceful Shutdown

[mrunalp]

Enhancement Description

• One-line enhancement description: Stop based based on their priority during node shutdown
• Kubernetes Enhancement Proposal: Pod priority based graceful node shutdown #2713
• Discussion Link:
• Primary contact (assignee): @mrunalp
• Responsible SIGs: sig-node
• Enhancement target (which target equals to which milestone):
  • Alpha release target (x.y): 1.22
  • Beta release target (x.y):
  • Stable release target (x.y):
• Alpha
  • KEP (k/enhancements) update PR(s): Pod priority based graceful node shutdown #2713
  • Code (k/k) update PR(s): Graceful Node Shutdown Based On Pod Priority kubernetes#102915
  • Docs (k/website) update PR(s): docs: Pod priority based graceful node shutdown website#30611

Please keep this description up to date. This will help the Enhancement Team to track the evolution of the enhancement efficiently.

[mrunalp]

/sig node

[ehashman]

/milestone v1.22

[jrsapi]

Greetings @mrunalp!
1.22 Enhancement shadow checking in. After reviewing the KEP and PRR this KEP will be marked tracked. A reminder that the enhancement freeze starts 5/13 23:59:59 PST.

Thanks!

[PI-Victor]

Hello @mrunalp 👋, 1.22 Docs release lead here.
This enhancement is marked as ‘Needs Docs’ for 1.22 release.

Please follow the steps detailed in the documentation to open a PR against dev-1.22 branch in the k/website repo. This PR can be just a placeholder at this time and must be created before Fri July 9, 11:59 PM PDT.
 Also, take a look at Documenting for a release to familiarize yourself with the docs requirement for the release.

Thank you!

[jrsapi]

Greetings @mrunalp,
Enhancement shadow checking with a reminder that we are 2 weeks away from code freeze (July 8, 2021). Can you confirm if the following k/k PR is all that is needed for the implementation of this enhancement for the 1.22 milestone?

• Pod Priority Based Node Graceful Shutdown

Thanks!

[jrsapi]

Greetings @mrunalp,
A reminder that this Thursday, July 8th is code freeze, and all PR's must be code complete and merged. This KEP is marked "At Risk" for the 1.22 milestone.

Also this Friday, July 9th is the Docs placeholder deadline and to open a PR follow the instructions above.

Thanks!

[jrsapi]

Greetings @mrunalp,
Sending a reminder that we have just one more day to get all open PRs merged before the code freeze deadline tomorrow Thursday, July 8th at 18:00 Pacific Time.

[mrunalp]

kubernetes/kubernetes#102915 is open for the implementation.

[JamesLaverack]

Hi, v1.22 Enhancements Lead here. Unfortunately this enhancement has not met the requirements for code freeze as kubernetes/kubernetes#102915 is unmerged and unapproved.

If you still wish to progress this enhancement in v1.22, then please file an exception request.

/milestone clear

[mrunalp]

We requested an exception for this.

[salaxander]

/milestone v1.23

[Priyankasaggu11929]

Hi @mrunalp! 1.23 Enhancements team here. Just checking in as we approach enhancements freeze on Thursday 09/09. Here's where this enhancement currently stands:

• KEP file using the latest template has been merged into the k/enhancements repo.
• KEP status is marked as implementable
• 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 for this one, we would just need the following to update:

• update issue description with the latest Enhancements target
• update keps/sig-node/2712-pod-priority-based-graceful-node-shutdown/kep.yaml to add the latest milestone.

Thank you!

[mrunalp]

@Priyankasaggu11929 I have opened a PR to update the milestone for the KEP.

[Priyankasaggu11929]

@mrunalp, thank you so much for the PR.

Could you please update this issue description as well with the latest Enhancement target. Would be really helpful to track the enhancement for the team. Thanks once again! :)

[Priyankasaggu11929]

Thanks so much for the changes, @mrunalp. With the KEP PR merged now, this enhancement is ready for the 1.23 enhancements freeze. :)

[rhockenbury]

Let me know if there are any updates on whether this is planned for beta for v1.24.

[mrunalp]

Hi yes we want to move this to beta. I will open a PR to update tomorrow.

…

On Jan 26, 2022, at 6:20 PM, Ryler Hockenbury ***@***.***> wrote:  Let me know if there are any updates on whether this is planned for beta for v1.24. — Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you were mentioned.

[mrunalp]

I opened a PR: #3194

[rhockenbury]

Thanks, please plan to merge #3194 before enhancements freeze at 18:00pm PT on Thursday Feb 3rd.

[rhockenbury]

I've moved this KEP to tracked for enhancement freeze. Thanks!

[PI-Victor]

Hi @mrunalp 👋 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 Thursday 31st March 2022, 18:00 PDT.

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

Thanks!

[valaparthvi]

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

[rhockenbury]

Hi @mrunalp

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 k/k#102915 has 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.

[ehashman]

That PR merged in 1.23. The PR for 1.24 is kubernetes/kubernetes#107986

[rhockenbury]

Got it. Thanks for the clarification.

[PI-Victor]

hi @mrunalp, the docs PR placeholder deadline is on the 31st of March, please open a docs placeholder Pr for these changes by then, thank you!

[nate-double-u]

@mrunalp Reminder that tomorrow (April 5th) is the deadline for 1.24 Docs Ready for Review.

Please open a PR, push your docs content for this enhancement, and remove the work-in-progress label when ready for review.

We have a tight turnaround to getting docs reviewed and approved for the release, and we’re hoping to have all docs in for review by tomorrow. Thank you!

[mrunalp]

I have opened kubernetes/website#32771

[k8s-triage-robot]

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

[pacoxu]

/remove-lifecycle stale
There seems to be no feedback about this feature yet.

[k8s-triage-robot]

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

[k8s-triage-robot]

The Kubernetes project currently lacks enough active 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 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 rotten

[k8s-triage-robot]

The Kubernetes project currently lacks enough active contributors to adequately respond to all issues and PRs.

This bot triages issues 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:

• Reopen this issue with /reopen
• Mark this issue as fresh with /remove-lifecycle rotten
• Offer to help out with Issue Triage

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

/close not-planned

[k8s-ci-robot]

@k8s-triage-robot: Closing this issue, marking it as "Not Planned".

In response to this:

The Kubernetes project currently lacks enough active contributors to adequately respond to all issues and PRs.

This bot triages issues 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:

• Reopen this issue with /reopen
• Mark this issue as fresh with /remove-lifecycle rotten
• Offer to help out with Issue Triage

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

/close not-planned

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.