KEP-4603: 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
• 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):
  • 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!

[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.

[lauralorenz]

Hi! Commented over there at kubernetes/kubernetes#122300 (comment)

[haircommander]

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

[impact-maker]

Hello @haircommander @lauralorenz 👋, v1.32 Enhancements team here.

Just checking in as we approach enhancements freeze on 02:00 UTC Friday 11th October 2024 / 19:00 PDT Thursday 10th October 2024.

This enhancement is targeting for stage alpha for v1.32 (correct me, if otherwise).

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.32.
• KEP readme has up-to-date graduation criteria.
• KEP has submitted a production readiness review request for approval and has a reviewer assigned.
• 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 3rd October 2024 so that the PRR team has enough time to review your KEP.

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

• KEP has submitted a production readiness review request for approval and has a reviewer assigned.
• 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 3rd October 2024 so that the PRR team has enough time to review your KEP.

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

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

[impact-maker]

@lauralorenz thanks! Everything looks good, I have updated the issue status to tracked for enhancements freeze

[chanieljdan]

Hi @lauralorenz 👋, 1.32 Release Docs Lead here.

Does this enhancement work planned for 1.32 require any new docs or modification to existing docs?

If so, please follows the steps here to open a PR against dev-1.32 branch in the k/website repo. This PR can be just a placeholder at this time and must be created before Thursday October 24th 2024 18:00 PDT.

Also, take a look at Documenting for a release to get yourself familiarize with the docs requirement for the release.

Thank you!

[rytswd]

Hi @lauralorenz 👋 -- this is Ryota (@rytswd) from the v1.32 Communications Team!

For the v1.32 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:

• This introduces some breaking change(s)
• This has significant impacts and/or implications to users
• ...Or this is a long-awaited feature, which would go a long way to cover the journey more in detail 🎉

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, 30th Oct 2024? For more information about writing a blog, please find the blog contribution guidelines 📚

Tip

Some timeline to keep in mind:

• 02:00 UTC Wednesday, 30th Oct: Feature blog PR freeze
• Monday, 25th Nov: Feature blogs ready for review
• You can find more in the release document

Note

In your placeholder PR, use XX characters for the blog date in the front matter and file name. We will work with you on updating the PR with the publication date once we have a final number of feature blogs for this release.

[chanieljdan]

Hi @lauralorenz 👋, 1.32 Release Docs Lead here.

Does this enhancement work planned for 1.32 require any new docs or modification to existing docs?

If so, please follows the steps here to open a PR against dev-1.32 branch in the k/website repo. This PR can be just a placeholder at this time and must be created before Thursday October 24th 2024 18:00 PDT.

Also, take a look at Documenting for a release to get yourself familiarize with the docs requirement for the release.

Thank you!

Hi @lauralorenz 👋,

Just a reminder to open a placeholder PR against dev-1.32 branch in the k/website repo for this (steps available here). The deadline for this is a week away at Thursday October 24, 2024 18:00 PDT.

Thanks,

Daniel

[lauralorenz]

Hi @chanieljdan, the placeholder PR is at kubernetes/website#48499. Thanks!

[chanieljdan]

Thanks Laura! 😄 🚀

[rytswd]

Hi @lauralorenz 👋, v1.32 Communications Team here again!

This is a gentle reminder for the feature blog deadline mentioned above, which is 02:00 UTC Wednesday, 30th Oct. To opt in, please let us know and open a Feature Blog placeholder PR against k/website by the deadline. If you have any questions, please feel free to reach out to us!

Tip

Some timeline to keep in mind:

• 02:00 UTC Wednesday, 30th Oct: Feature blog PR freeze
• Monday, 25th Nov: Feature blogs ready for review
• You can find more in the release document

Note

In your placeholder PR, use XX characters for the blog date in the front matter and file name. We will work with you on updating the PR with the publication date once we have a final number of feature blogs for this release.

[lauralorenz]

Hiya @rytswd, yes I would like to add a blog post and have made the placeholder PR at kubernetes/website#48589. Thanks!