Tune CrashLoopBackOff

[lauralorenz]

Enhancement Description

• One-line enhancement description (can be used as a release note): Tune CrashLoopBackoff
• Kubernetes Enhancement Proposal: https://github.com/kubernetes/enhancements/blob/master/keps/sig-node/4603-tune-crashloopbackoff/README.md
• Discussion Link: A mechanism to fail a Pod that is stuck due to an invalid Image kubernetes#122300 (comment)
• Primary contact (assignee): @lauralorenz
• Responsible SIGs: SIG-Node
• Enhancement target (which target equals to which milestone):
  • Alpha release target (x.y): 1.32
  • Beta release target (x.y): 1.34
  • Stable release target (x.y): 1.36
• See also project board (Done excluded) here
• Alpha
  • KEP (k/enhancements) update PR(s):
    • KEP-4603: initial KEP for Tune CrashLoopBackoff #4604
    • KEP-4603: Update crashloopbackoff for 1.32 lauralorenz/enhancements#21
    • KEP-4603: tune crashloopbackoff for 1.32 #4893
    • KEP-4603: PRR testgrid/prow link updates #4910
  • Code (k/k) update PR(s):
    • KEP-4603: Refactor various hardcoded backoffs into separate constants kubernetes#128369
    • KEP-4603: Maintain current 10 minute recovery threshold for container backoff regardless of changes to the maximum duration kubernetes#128356
    • KEP-4603: Node specific kubelet config for maximum backoff down to 1 second kubernetes#128374
    • E2E Node tests for image pull backoff and crashloopbackoff behavior kubernetes#128559
  • Docs (k/website) update PR(s):
    • KEP-4602: Crashloopbackoff alpha docs PR website#48499
• Alpha2
  • [WIP] Add blog post on alpha changes to CrashLoopBackOff website#48589

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!

[mickeyboxell]

Hi @lauralorenz, I wanted to follow up again prior to the enhancements freeze tomorrow. Do you think you'll have some time today or tomorrow to address the comments above?

[lauralorenz]

Thanks for following up @mickeyboxell! This is going to get bumped to 1.32. You can take it off your radar. Thanks!

[dipesh-rawat]

Hello @lauralorenz 👋, 1.31 Enhancements team here.

Since this enhancement has been rescheduled for a future release, it’s now marked as Deferred for the current v1.31 release cycle. Confirming this based on the comment #4603 (comment). Thanks!

/milestone clear
/remove-label lead-opted-in

[k8s-ci-robot]

@dipesh-rawat: You must be a member of the kubernetes/milestone-maintainers GitHub team to set the milestone. If you believe you should be able to issue the /milestone command, please contact your Milestone Maintainers Team and have them propose you as an additional delegate for this responsibility.

In response to this:

Hello @lauralorenz 👋, 1.31 Enhancements team here.

Since this enhancement has been rescheduled for a future release, it’s now marked as Deferred for the current v1.31 release cycle. Confirming this based on the comment #4603 (comment). Thanks!

/milestone clear
/remove-label lead-opted-in

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.

[SergeyKanzhelev]

/milestone clear
/remove-label lead-opted-in

[k8s-ci-robot]

@SergeyKanzhelev: Those labels are not set on the issue: lead-opted-in

In response to this:

/milestone clear
/remove-label lead-opted-in

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.

[sreeram-venkitesh]

/label tracked/no

[kannon92]

@lauralorenz @tallclair wdyt of kubernetes/kubernetes#122300? I think having a max limit on back off and then setting pod to failed would be useful and I’m curious if we can expand this feature.

[sftim]

We don't put IDs in KEP titles, so:
/retitle Tune CrashLoopBackOff

[haircommander]

/reopen

A github workflow autoclosed when I set to done 🙃 sorry for the noise

[dipesh-rawat]

Hello @lauralorenz 👋, 1.33 Enhancements Lead here.

I’m closing milestone 1.32 now. If you'd like to work on this enhancement in v1.33, please have the SIG lead opt-in by adding the lead-opted-in label, which ensures it gets added to the tracking board. Also, please set the milestone to v1.33 using /milestone v1.33.
Thanks!

/remove-label lead-opted-in
/milestone clear

[lauralorenz]

FYI there is a separate project board for just this KEP tracking the current work that is here (this link is also now in the OP too). For 1.33 this is not a change in maturity level but continuing work for an alpha2.

[haircommander]

/label lead-opted-in
/milestone v1.33

[ArkaSaha30]

Hello @lauralorenz 👋, 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 alpha once again for v1.33 (correct me, if otherwise)
/stage alpha

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.33.
• 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 on Thursday 6th February 2025 so that the PRR team has enough time to review your KEP.

For this KEP, we would just need to update the following:

• KEP needs to reflect the latest-milestone: "v1.33"

The status of this enhancement is marked as At risk for enhancements freeze. Please keep the issue description up-to-date with appropriate stages as well.

If you anticipate missing enhancements freeze, you can file an exception request in advance. Thank you!

[kannon92]

FYI there is a separate project board for just this KEP tracking the current work that is here (this link is also now in the OP too). For 1.33 this is not a change in maturity level but continuing work for an alpha2.

@lauralorenz

Can you do the milestone bump so this can be correctly tracked?

[dipesh-rawat]

Hi @lauralorenz 👋, 1.33 Enhancements team here,

Just a quick friendly reminder as we approach the enhancements freeze later this week, at 02:00 UTC Friday 14th February 2025 / 19:00 PDT Thursday 13th February 2025.

The current status of this enhancement is marked as At risk for enhancement freeze. There are a few requirements mentioned in the comment #4603 (comment) that still need to be completed.

If you anticipate missing enhancements freeze, you can file an exception request in advance. Thank you!

[dipesh-rawat]

Hello @lauralorenz 👋, 1.33 Enhancements team here,

Now that PR #5164 been merged, all the KEP requirements are in place and merged into k/enhancements, this enhancement is all good for the upcoming enhancements freeze. 🚀

The status of this enhancement is marked as tracked for enhancement freeze. Please keep the issue description up-to-date with appropriate stages as well. Thank you!

(cc: @ArkaSaha30)

/label tracked/yes