KEP-4603: Tune CrashLoopBackoff

[lauralorenz]

Enhancement Description

• One-line enhancement description (can be used as a release note): Tune CrashLoopBackoff
• Kubernetes Enhancement Proposal: [WIP] KEP-4603: initial KEP for Tune CrashLoopBackoff #4604
• Discussion Link:
• Primary contact (assignee): lauralorenz@
• Responsible SIGs: SIG-Node
• Enhancement target (which target equals to which milestone):
  • Alpha release target (x.y): 1.31
  • Beta release target (x.y): 1.33
  • Stable release target (x.y): 1.35
• Alpha
  • KEP (k/enhancements) update PR(s): [WIP] KEP-4603: initial KEP for Tune CrashLoopBackoff #4604
  • Code (k/k) update PR(s):
  • Docs (k/website) update PR(s):

Please keep this description up to date. This will help the Enhancement Team to track the evolution of the enhancement efficiently.

[SergeyKanzhelev]

/label lead-opted-in
/milestone v1.31
/assign @lauralorenz

[SergeyKanzhelev]

/sig node

[SergeyKanzhelev]

/stage alpha

[mickeyboxell]

Hi @lauralorenz 👋 v1.31 Enhancements team here.

I wanted to check in as we approach the enhancements freeze on 02:00 UTC Friday 14th June 2024 / 19:00 PDT Thursday 13th June 2024.

This enhancement is targeting alpha for v1.31. Please correct me if that isn't the case.

Here's where this enhancement currently stands:

• KEP readme using the latest template has been merged into the k/enhancements repo.
• KEP status is marked as implementable for latest-milestone: v1.31. KEPs targeting stable will need to be marked as implemented after code PRs are merged and the feature gates are removed.
• KEP readme has up-to-date graduation criteria
• KEP has a production readiness review that has been completed and merged into k/enhancements. (For more information on the PRR process, check here). If your production readiness review is not completed yet, please make sure to fill the production readiness questionnaire in your KEP by the PRR Freeze deadline so that the PRR team has enough time to review your KEP before the enhancements freeze.

For this KEP, we need to do the following:

• Get https://github.com/kubernetes/enhancements/pull/4604/files#diff-ffa07b017bd73874c1a805a8492f4e83e1d334445fcf891da0be617332650427 merged prior to the enhancements freeze.
• Please share a link to the PRR approval and if it has not yet been approved make sure to do so by the deadline mentioned above.

The status of this enhancement is marked as at risk for enhancement freeze. We can mark it as tracked as soon as the above changes are merged. Please make sure to get this done before the enhancements freeze.

If you anticipate missing enhancements freeze, you can file an exception request in advance. Let me know if you have any questions! Thank you!