-
Notifications
You must be signed in to change notification settings - Fork 1.5k
Backoff Limit Per Index For Indexed Jobs #3850
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
Comments
/sig apps |
/assign @mimowo |
In addition to configuring the backoff per index, we should probably have |
/milestone v1.28 |
Hello @mimowo 👋, 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 |
@aramase is there anything missing to make it tracked? |
Hey @mimowo The status of this enhancement is marked as |
Hello @mimowo 👋, 1.28 Docs Lead here. Does this enhancement work planned for 1.28 require any new docs or modification to existing docs? If so, please follows the steps here to open a PR against Also, take a look at Documenting for a release to get yourself familiarize with the docs requirement for the release. Thank you! |
Hey again @mimowo 👋 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:
I see kubernetes/kubernetes#118009 PR in the issue description. 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! |
Hey @mimowo 👋 Enhancements Lead here, |
Hello @mimowo @soltysh 👋, v1.33 Enhancements team here. Just checking in as we approach enhancements freeze on 02:00 UTC Friday 14th February 2025 / 19:00 PDT Thursday 13th February 2025. This enhancement is targeting stage Here's where this enhancement currently stands:
For this KEP, we would just need to update the following:
The status of this enhancement is marked as If you anticipate missing enhancements freeze, you can file an exception request in advance. Thank you! |
I will not have the capacity to work on this in the release cycle. I'm happy to help with reviews if there are other contributors. Otherwise I will try to book time for it in the next cycle. |
Actually, let me give it a shot in this iteration. I think it should be relatively little work to do: #5154 |
@mimowo thank you - it's now tracked! |
Hello, @mimowo @soltysh 👋, v1.33 Docs Shadow here. Does this enhancement work planned for v1.33 require any new docs or modifications to existing docs? If so, please follow the steps here to open a PR against the dev-1.33 branch in the k/website repo. This PR can be just a placeholder at this time and must be created before Thursday 27th February 2025 18:00 PDT. Also, take a look at Documenting for a release to get yourself familiarized with the docs requirement for the release. Thank you! |
I have opened the website PR: kubernetes/website#49811 |
Great! Please also update the issue description with the PR link :) Thank you, @mimowo! |
cc @jensentanlo please update the Issue description with the code and docs PRs |
Hi @mimowo 👋 -- this is Ryota (@rytswd) from the 1.33 Communications Team! For the 1.33 release, we are currently in the process of collecting and curating a list of potential feature blogs, and we'd love for you to consider writing one for your enhancement! As you may be aware, feature blogs are a great way to communicate to users about features which fall into (but not limited to) the following categories:
To opt in to write a feature blog, could you please let us know and open a "Feature Blog placeholder PR" (which can be only a skeleton at first) against the website repository by Wednesday, 5th March, 2025? For more information about writing a blog, please find the blog contribution guidelines 📚 Tip Some timeline to keep in mind:
Note In your placeholder PR, use |
Hi @rytswd, yes, I would like to opt-in, opened the placeholder PR: kubernetes/website#49982 |
Hey again @mimowo @soltysh 👋, v1.33 Enhancements team here. Just checking in as we approach code freeze at 02:00 UTC Friday 21st March 2025 / 19:00 PDT Thursday 20th March 2025. Here's where this enhancement currently stands:
Per the issue description, these are all of the implementation (code-related) PRs for 1.33:
Please let me know (and keep the issue description updated) if there are any other PRs in k/k that we should track for this KEP, so that we can maintain accurate status. This enhancement is now marked as Please note that KEPs targeting |
Sure, I opened a PR to update it: #5186. |
Enhancement Description
One-line enhancement description (can be used as a release note): Add New Indexed Job backoff limit mode that is counted per index rather than per job
Kubernetes Enhancement Proposal: https://github.com/kubernetes/enhancements/tree/master/keps/sig-apps/3850-backoff-limits-per-index-for-indexed-jobs
Discussion Link: An Indexed Job mode that allows every index to execute kubernetes#109712
Primary contact (assignee): mimowo
Responsible SIGs: apps
Enhancement target (which target equals to which milestone):
Alpha
k/enhancements
) update PR(s): Backoff limit per Job Index #3967k/k
) update PR(s):k/website
) update PR(s): Docs update for Job's backoff limit per index (alpha in 1.28) website#41921Beta
k/enhancements
) update PR(s):k/k
) update PR(s):k/website
) update(s): Docs update for Job Backoff Limit Per Index in Beta website#43388Stable
k/enhancements
) update PR(s): KEP3850: graduate Backoff Limit Per Index for Job to stable #5154k/k
) update PR(s):k/website
) update(s): Docs update as we promote JobBackoffLimitPerIndex to stable website#49811Please 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: