-
Notifications
You must be signed in to change notification settings - Fork 1.4k
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
Allow for recreation of pods once fully terminated in the job controller #3939
Comments
/sig apps |
/cc @wangyysde |
/assign |
/stage alpha |
Hello @alculquicondor 👋, Enhancements team here. Just checking in as we approach enhancements freeze on 01:00 UTC Friday, 16th June 2023. This enhancement is targeting for stage Here's where this enhancement currently stands:
The status of this enhancement is marked as |
Hey @alculquicondor @kannon92 The status of this enhancement is marked as |
Thank you so much to @alculquicondor for taking this over while I was on PTO. It is so exciting to see that this is tracked for this release. @alculquicondor reached out and I will take over the implementation of this PR. /assign |
Hey again @alculquicondor @kannon92 👋 Just checking in as we approach Code freeze at 01:00 UTC Friday, 19th July 2023 . Here’s the enhancement’s state for the upcoming code freeze:
If there are any other k/k related PR(s) that we should be tracking for this KEP please link them in the issue description above. As always, we are here to help if any questions come up. Thanks! |
Thanks for filling an exception request! I'll reapply the v1.28 milestone if the exception request is approved. |
/milestone clear |
Thanks for the reminder. I created kubernetes/website#43529 @kannon92 could you update the issue description? |
Hi @kannon92 @alculquicondor @dejanzele 👋 from the v1.29 Release Team-Communications! We would like to check if you have any plans to publish a blog for this KEP regarding new features, removals, and deprecations for this release. If so, you need to open a PR placeholder in the website repository. |
Thanks for the reminder @kcmartin. We did one for 1.28 https://kubernetes.io/blog/2023/08/21/kubernetes-1-28-jobapi-update/ |
Hey again @kannon92 @dejanzele @alculquicondor! 👋 v1.29 Enhancements team here, Just checking in as we approach code freeze at 01:00 UTC Wednesday 1st November 2023 . Here's where this enhancement currently stands:
This KEP is Also, please let me know if there are other PRs in k/k we should be tracking for this KEP. As always, we are here to help if any questions come up. Thanks! |
Hello @kannon92 @dejanzele @alculquicondor 👋, 1.29 Enhancements team here! With all the implementation (code related) PRs merged as per the issue description, this enhancement is now marked as The test freeze is 01:00 UTC Wednesday 15th November 2023 / 18:00 PDT Tuesday 14th November 2023. Please make sure all test PRs are merged in by then. The tracked test PRs for this KEP are: Please let me know if there are additional test PRs we should track. Thanks! |
The open PR just updates the KEP with the changes we decided during the implementation reviews. But all the test code is already merged. |
Ah okay, thanks for clarifying! This means that there are no more PRs to be merged into k/k for this KEP right? |
@sreeram-venkitesh, In my opinion, we merged everything which is required for PodReplacementPolicy to go into Beta and the requirements are done. |
k/website is not quite done but code freeze wise, we are looking good. |
I updated this checklist. I think we have each component necessary for 1.29 now and we are good to go for 1.29. Thank you @dejanzele for leading this effort. And thank you to @alculquicondor for doing the necessary docs updates! |
/remove-label lead-opted-in |
Hello 👋 1.30 Enhancements Lead here, I'm closing milestone 1.29 now, /milestone clear |
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 |
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
One-line enhancement description (can be used as a release note): For Job controllers we want to optionally include a way for users to include terminating pods in the active pod count.
Kubernetes Enhancement Proposal: https://github.com/kubernetes/enhancements/tree/master/keps/sig-apps/3939-allow-replacement-when-fully-terminated
Discussion Link: Jobs create replacement Pods as soon as a Pod is marked for deletion kubernetes#115844
Primary contact (assignee): @kannon92, @dejanzele
Responsible SIGs: sig-apps
Enhancement target (which target equals to which milestone):
Alpha
k/enhancements
) update PR(s): KEP-3939: Consider terminating pods in job controller #3940k/k
) update PR(s):k/website
) update PR(s):Beta
k/enhancements
) update PR(s): KEP-3939: promote to beta in 1.29. #4252k/k
) update PR(s):k/website
) update(s):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: