Evacuation API

[atiratree]

Enhancement Description

• One-line enhancement description (can be used as a release note): introduce Evacuation API to allow managed graceful pod removal
• Kubernetes Enhancement Proposal: KEP-4563: Evacuation API #4565
• Discussion Link: Declarative Node Maintenance #4212 (part of the functionality has been split into this KEP)
• Primary contact (assignee): @atiratree
• Responsible SIGs: sig-apps
• Enhancement target (which target equals to which milestone):
  • Alpha release target (x.y): 1.31
  • Beta release target (x.y):
  • Stable release target (x.y):
• Alpha
  • KEP (k/enhancements) update PR(s): KEP-4563: Evacuation API #4565
  • Code (k/k) update PR(s):
  • Docs (k/website) update PR(s):

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

[atiratree]

/sig apps

[soltysh]

/assign @atiratree

/label lead-opted-in
/stage alpha
/milestone v1.31

[dipesh-rawat]

Hello @atiratree 👋, 1.31 Enhancements team here.

Just checking in as we approach enhancements freeze on on 02:00 UTC Friday 14th June 2024 / 19:00 PDT Thursday 13th June 2024.

This enhancement is targeting for stage alpha for 1.31 (correct me, if otherwise)

Here's where this enhancement currently stands:

• KEP readme using the latest template has been merged into the k/enhancements repo.
• KEP status is marked as implementable for latest-milestone: v1.31. KEPs targeting stable will need to be marked as implemented after code PRs are merged and the feature gates are removed.
• KEP readme has up-to-date graduation criteria
• KEP has a production readiness review that has been completed and merged into k/enhancements. (For more information on the PRR process, check here).

For this KEP, we would need to update the following:

• Create the KEP readme using the latest template and merge it in the k/enhancements repo.
• Ensure that the KEP has undergone a production readiness review and has been merged into k/enhancements.

It looks like #4565 will address most of these issues.

• Get KEP-4563: Evacuation API #4565 merged before the enhancements freeze.

The status of this enhancement is marked as at risk for enhancement freeze. Please keep the issue description up-to-date with appropriate stages as well. Thank you!

[soltysh]

This and #4212 where discussed heavily again during Monday's SIG-Apps call, with the general hesitation from SIG leads we're going to hold on with these efforts in favor of looking into extending PDB and eviction API.

/milestone clear
/remove-label lead-opted-in

[dipesh-rawat]

Hello 👋, 1.31 Enhancements team here.

Since this enhancement has been rescheduled for a future release, it’s now marked as Deferred for the current v1.31 release cycle. Confirming this based on the comment #4563 (comment) Thanks!

[sreeram-venkitesh]

/label tracked/no

[k8s-triage-robot]

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

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

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

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

/lifecycle stale