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
Pod Scheduling Readiness #3521
Comments
/sig scheduling |
/label lead-opted-in |
/milestone v1.26 |
Hey @kerthcet 👋, 1.26 Enhancements team here! Just checking in as we approach Enhancements Freeze on 18:00 PDT on Thursday 6th October 2022. This enhancement is targeting for stage Here's where this enhancement currently stands:
For this KEP, we would need to:
The status of this enhancement is marked as |
Thanks @Atharva-Shinde.
|
Hello @Huang-Wei 👋, just a quick check-in again, as we approach the 1.26 Enhancements freeze. Please plan to get the PR #3522 merged before Enhancements freeze on 18:00 PDT on Thursday 6th October 2022 i.e tomorrow For note, the current status of the enhancement is marked |
Thanks for the reminder. It's 99% accomplished atm, just some final comments waiting for the approver to +1. |
With #3522 merged, we have this marked as |
Hi @Huang-Wei 👋, Checking in once more as we approach 1.26 code freeze at 17:00 PDT on Tuesday 8th November 2022. Please ensure the following items are completed:
For this enhancement, it looks like the following PRs are open and need to be merged before code freeze:
Please ensure all of these PRs are linked to this issue as well and mentioned in the initial issue description. As always, we are here to help should questions come up. Thanks! |
@marosset yes, those 3 PRs are code implementation for this KEP in alpha stage. I just updated the issue description to get them linked. |
Hello @Huang-Wei 👋, 1.26 Release Docs Lead here. This enhancement is marked as ‘Needs Docs’ for 1.26 release. Please follow the steps detailed in the documentation to open a PR against Any doubt, reach us! Thank you! |
Hi @Huang-Wei 👋, Checking in once more as we approach 1.26 code freeze at 17:00 PDT on Tuesday 8th November 2022. Please ensure the following items are completed:
For this enhancement, it looks like the following PRs are open and need to be merged before code freeze:
As always, we are here to help should questions come up. Thanks! |
@marosset ACK, I'm working with reviewers to get 2 pending PRs merged by tomorrow. |
All dev work has been merged. |
/remove-label lead-opted-in |
Not sure if I should post this here or #2926, but it would be nice if scheduling gates are mutable in the job template. |
/label lead-opted-in |
If we graduate this to beta, we'll need to update https://kubernetes.io/docs/concepts/workloads/pods/pod-lifecycle/ and maybe other Pod pages, to mention / link to the details about it. |
/stage beta |
Hello @Huang-Wei 👋, Enhancements team here. Just checking in as we approach enhancements freeze on 18:00 PDT Thursday 9th February 2023. This enhancement is targeting for stage Here's where this enhancement currently stands:
It looks like #3739 will address these issues. The status of this enhancement is marked as |
Looks like with #3739 merged this enhancement as tracked for v1.27. /remove-label tracked/no |
Hi @Huang-Wei, Checking in as we approach 1.27 code freeze at 17:00 PDT on Tuesday 14th March 2023. Please ensure the following items are completed:
For this enhancement, it looks like the following PRs are open and need to be merged before code freeze:
Please let me know if there are any other PRs in k/k I should be tracking for this KEP. |
@npolshakova I will have my eye on kubernetes/kubernetes#116201 to ensure it's completed before code freeze. |
https://kubernetes.io/docs/concepts/workloads/pods/#pod-update-and-replacement |
Enhancement Description
schedulingGates
field to the Pod spec that marks a Pod's scheduling readiness.Alpha
scheduler_pending_pods
metric kubernetes#113946Beta
Please 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: