-
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) |
/milestone v1.32 |
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:
For this KEP, we would need to update the following:
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! |
@lauralorenz thanks! Everything looks good, I have updated the issue status to tracked for enhancements freeze |
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 👋 -- 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:
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:
Note In your placeholder PR, use |
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 |
Hi @chanieljdan, the placeholder PR is at kubernetes/website#48499. Thanks! |
Thanks Laura! 😄 🚀 |
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 Tip Some timeline to keep in mind:
Note In your placeholder PR, use |
Hiya @rytswd, yes I would like to add a blog post and have made the placeholder PR at kubernetes/website#48589. Thanks! |
Enhancement Description
k/enhancements
) update PR(s):k/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: