-
Notifications
You must be signed in to change notification settings - Fork 1.5k
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
KEP-4603: Tune CrashLoopBackoff #4603
Comments
/label lead-opted-in |
/sig node |
/stage alpha |
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:
For this KEP, we need to do the following:
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! |
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? |
Thanks for following up @mickeyboxell! This is going to get bumped to 1.32. You can take it off your radar. Thanks! |
Hello @lauralorenz 👋, 1.31 Enhancements team here. Since this enhancement has been rescheduled for a future release, it’s now marked as /milestone clear |
@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:
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. |
/milestone clear |
@SergeyKanzhelev: Those labels are not set on the issue: In response to this:
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. |
/label tracked/no |
@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. |
Hi! Commented over there at kubernetes/kubernetes#122300 (comment) |
Enhancement Description
k/enhancements
) update PR(s): KEP-4603: initial KEP for Tune CrashLoopBackoff #4604k/k
) update PR(s):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.
The text was updated successfully, but these errors were encountered: