Scale down a deployment by removing specific pods (PodDeletionCost)

[ahg-g]

Enhancement Description

• One-line enhancement description (can be used as a release note): allow users to decide which pods should be scaled first
• Kubernetes Enhancement Proposal: WIP
• Discussion Link: Scale down a deployment by removing specific pods kubernetes#45509
• Primary contact (assignee): @drbugfinder-work, @ahg-g
• Responsible SIGs: sig-apps
• Enhancement target (which target equals to which milestone):
  • Alpha release target (1.21):
  • Beta release target (1.22):
  • Stable release target (1.24):
• Alpha
  • KEP (k/enhancements) update PR(s): https://github.com/kubernetes/enhancements/tree/master/keps/sig-apps/2255-pod-cost
  • Code (k/k) update PR(s): Implements pod deletion cost kubernetes#99163
  • Docs (k/website) update PR(s): ReplicaSet pod-deletion-cost annotation website#26739
• Beta
  • KEP (k/enhancements) update PR(s): Promote PodDeletionCost to Beta #2619
  • Code (k/k) update PR(s): Graduate PodDeletionCost to Beta kubernetes#101080, Integration test for pod deletion cost feature kubernetes#101003
  • Docs (k/website) update(s): PodDeletionCost to Beta website#28417

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

[ahg-g]

/sig apps

[ahg-g]

@annajung @JamesLaverack james, you mentioned in the sig-apps slack channel that this enhancement is at risk, can you clarify why? it meets the criteria.

[JamesLaverack]

@ahg-g Just to follow up here too, we discussed in Slack and this was due to a delay in reviewing. We've now marked this as "Tracked" on the enhancements spreadsheet for 1.21.

Thank you for getting back to us. :)

[JamesLaverack]

Hi @ahg-g,

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!