-
Notifications
You must be signed in to change notification settings - Fork 1.5k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Scale down a deployment by removing specific pods (PodDeletionCost) #2255
Comments
/sig apps |
@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. |
@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. :) |
Hi @ahg-g, Since your Enhancement is scheduled to be in 1.21, please keep in mind the important upcoming dates:
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! |
done. |
Hi @ahg-g Enhancements team is currently tracking the following PRs As this PR is merged, can we mark this enhancement complete for code freeze or do you have other PR(s) that are being worked on as part of the release? |
Hi @JamesLaverack , yes the k/k code is merged, docs PR still open though. |
/stage beta |
/milestone v1.22 |
/remove-lifecycle stale |
The Kubernetes project currently lacks enough contributors to adequately respond to all issues. This bot triages un-triaged issues according to the following rules:
You can:
Please send feedback to sig-contributor-experience at kubernetes/community. /lifecycle stale |
/remove-lifecycle stale |
would the following be an acceptable design pattern?
|
The Kubernetes project currently lacks enough contributors to adequately respond to all issues. This bot triages un-triaged issues according to the following rules:
You can:
Please send feedback to sig-contributor-experience at kubernetes/community. /lifecycle stale |
/remove-lifecycle stale |
The Kubernetes project currently lacks enough contributors to adequately respond to all issues. This bot triages un-triaged issues according to the following rules:
You can:
Please send feedback to sig-contributor-experience at kubernetes/community. /lifecycle stale |
/remove-lifecycle stale |
The Kubernetes project currently lacks enough contributors to adequately respond to all issues. This bot triages un-triaged issues according to the following rules:
You can:
Please send feedback to sig-contributor-experience at kubernetes/community. /lifecycle stale |
superceded by kubernetes/kubernetes#123541 ? |
@ddelange my proposal in kubernetes/kubernetes#123541 is the logical continuation of this KEP, and is fully backward compatible as currently written. But I note that this KEP never made it to "Stable", and the Before the feature can be considered stable I think we should aim to implement kubernetes/kubernetes#123541, as without it, it's too appealing for users to use it wrong (e.g. create controller which spam updates the With my proposal, users can inject the required |
The Kubernetes project currently lacks enough active contributors to adequately respond to all issues. This bot triages un-triaged issues according to the following rules:
You can:
Please send feedback to sig-contributor-experience at kubernetes/community. /lifecycle rotten |
/remove-lifecycle rotten |
Enhancement Description
k/enhancements
) update PR(s): https://github.com/kubernetes/enhancements/tree/master/keps/sig-apps/2255-pod-costk/k
) update PR(s): Implements pod deletion cost kubernetes#99163k/website
) update PR(s): ReplicaSet pod-deletion-cost annotation website#26739k/enhancements
) update PR(s): Promote PodDeletionCost to Beta #2619k/k
) update PR(s): Graduate PodDeletionCost to Beta kubernetes#101080, Integration test for pod deletion cost feature kubernetes#101003k/website
) update(s): PodDeletionCost to Beta website#28417Please keep this description up to date. This will help the Enhancement Team to track the evolution of the enhancement efficiently.
The text was updated successfully, but these errors were encountered: