enhancements: Allow for recreation of pods once fully terminated in the job controller
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: https://github.com/kubernetes/kubernetes/issues/115844
-
Primary contact (assignee): @kannon92, @dejanzele
-
Responsible SIGs: sig-apps
-
Enhancement target (which target equals to which milestone):
- Alpha release target (x.y): 1.28
- Beta release target (x.y): 1.29
- Stable release target (x.y):
-
Alpha
- KEP (
k/enhancements) update PR(s): https://github.com/kubernetes/enhancements/pull/3940 - Code (
k/k) update PR(s):- Job API - https://github.com/kubernetes/kubernetes/pull/119301
- Job Controller Changes - https://github.com/kubernetes/kubernetes/pull/117015
- PodGC - https://github.com/kubernetes/kubernetes/pull/118772
- Docs (
k/website) update PR(s):- Job Section - https://github.com/kubernetes/website/pull/41745
- Alpha Blog Post - https://github.com/kubernetes/website/pull/41924
- KEP (
-
Beta
- KEP (
k/enhancements) update PR(s): https://github.com/kubernetes/enhancements/pull/4252 - Code (
k/k) update PR(s):- https://github.com/kubernetes/kubernetes/pull/119912
- https://github.com/kubernetes/kubernetes/pull/121011
- https://github.com/kubernetes/kubernetes/pull/121147
- https://github.com/kubernetes/kubernetes/pull/121274
- https://github.com/kubernetes/kubernetes/pull/121342
- Metrics addition: https://github.com/kubernetes/kubernetes/pull/121481
- Feature Enable and E2E Tests: https://github.com/kubernetes/kubernetes/pull/121491
- Docs (
k/website) update(s):
- KEP (
Please keep this description up to date. This will help the Enhancement Team to track the evolution of the enhancement efficiently.
About this issue
- Original URL
- State: open
- Created a year ago
- Comments: 39 (29 by maintainers)
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!
Thanks for the reminder. I created https://github.com/kubernetes/website/pull/43529
@kannon92 could you update the issue description?
k/website is not quite done but code freeze wise, we are looking good.
@sreeram-venkitesh, In my opinion, we merged everything which is required for PodReplacementPolicy to go into Beta and the requirements are done.
Thanks for the reminder @kcmartin. We did one for 1.28 https://kubernetes.io/blog/2023/08/21/kubernetes-1-28-jobapi-update/ We are not thinking of another one this time.
You need to start by sending a PR to kubernetes/enhancements to update the stage to beta and get the approval from SIG Apps.
Sig-Apps is the team that owns this feature. I am not sure if planning has happened for 1.29 for sig-apps.
I know that @alculquicondor and @mimowo would like to have this promoted to beta.
You can look at the KEP and see what items are required for beta.
I believe we stated the following items:
I’m afraid I won’t have capacity this release to take this work on. Luckily @dejanzele has asked to take on some of this work.
/assign @dejanzele
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:
approvedandlgtmlabels applied) by the code freeze deadline. This includes any tests related PR/s too.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!