-
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
Restarting sidecar containers during Pod termination #4438
Comments
/sig node |
/stage alpha |
/label lead-opted-in |
Hello @matthyx 👋, Enhancements team here. Just checking in as we approach enhancements freeze on 02:00 UTC Friday 9th February 2024. This enhancement is targeting for stage Here's where this enhancement currently stands:
The status of this enhancement is marked as |
Hi @matthyx , 👋 from the v1.30 Communications Team! We'd love for you to opt in to write a feature blog about your enhancement! We encourage blogs for features including, but not limited to: breaking changes, features and changes important to our users, and features that have been in progress for a long time and are graduating. To opt in, you need to open a Feature Blog placeholder PR against the website repository. |
|
Hello @matthyx 👋, v1.30 Docs Shadow here. Does this enhancement work planned for v1.30 require any new docs or modification to existing docs? If so, please follows the steps here to open a PR against dev-1.30 branch in the k/website repo. This PR can be just a placeholder at this time and must be created before Thursday, February 22nd, 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!
A feature gate is being added, so we'll need docs, marking it as |
Hey again @matthyx 👋 Enhancements team here, Just checking in as we approach code freeze at 02:00 UTC Wednesday 6th March 2024 . Here's where this enhancement currently stands:
Also, please let me know if there are other PRs in k/k we should be tracking for this KEP, I didn't see any in the description |
@AnaMMedina21 this is the main PR kubernetes/kubernetes#121412 however I'm not sure it will be finished on time... |
@AnaMMedina21 we have missed code freeze, let's try again for 1.31 |
@AnaMMedina21 I updated the status to |
/milestone clear |
Hi 👋, 1.31 Enhancements Lead here. If you wish to progress this enhancement in v1.31, please have the SIG lead opt-in your enhancement by adding the lead-opted-in label and set the milestone to v1.31 before the Production Readiness Review Freeze. /remove-label lead-opted-in |
/label lead-opted-in |
@LaurentGoderre I will reopen the docs PR to cover the new flag, and I think it's a good idea to mention that in the termination page 👍 |
Hi @matthyx, 👋 from the v1.31 Communications Team! We'd love for you to opt in to write a feature blog about your enhancement! To opt in, let us know and open a Feature Blog placeholder PR against the website repository by 3rd July, 2024. For more information about writing a blog see the blog contribution guidelines. Note: In your placeholder PR, use |
Hey @matthyx, friendly reminder about the upcoming blog opt-in and placeholder deadline on July 3rd. Please open a blog placeholder PR if you are interested in contributing a blog. |
@matthyx |
|
Hey again @matthyx @gjkim42 👋 v1.31 Enhancements team here, Just checking in as we approach code freeze at 02:00 UTC Wednesday 24th July 2024 / 19:00 PDT Tuesday 23rd July 2024. Here's where this enhancement currently stands:
For this enhancement, it looks like the following PRs are open and need to be merged before code freeze (and we need to update the Issue description to include all the related PRs of this KEP): If you anticipate missing code freeze, you can file an exception request in advance. Marking this KEP as |
Hi again @matthyx! We're a week away from the code freeze deadline and I wanted to ping you as a slight reminder for getting kubernetes/kubernetes#125710 merged in time before the deadline. Please let me know if there are any other PRs that we should be tracking as well. Thanks! |
@matthyx could you also please add that PR link tot the issue description. |
Hello @matthyx @gjkim42 👋 v1.31 Enhancements team here, Unfortunately, the implementation (code related) PR(s) associated with this enhancement is not in the merge-ready state by code-freeze and hence this enhancement is now removed from the v1.31 milestone. If you still wish to progress this enhancement in v1.31, please file an exception request as soon as possible, within three days. If you have any questions, you can reach out in the #release-enhancements channel on Slack and we'll be happy to help. Thanks! /milestone clear |
Are you planning to work on the implementation in 1.32? |
yes if we can have the review cycles of @smarterclayton :) |
Hi, enhancements lead here - I inadvertently added this to the 1.32 tracking board 😀. Please readd it if you wish to progress this enhancement in 1.32. /remove-label lead-opted-in |
/milestone v1.32 |
Hello @matthyx 👋, 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 Here's where this enhancement currently stands:
For this KEP, we would just need to update the following:
The status of this enhancement is marked as If you anticipate missing enhancements freeze, you can file an exception request in advance. Thank you! |
|
@matthyx with all the requirements met, this enhancement is now |
Hello @matthyx 👋 from the v1.32 Communications Team! To opt-in, let us know and open a Feature Blog placeholder PR against the website repository by 30th Oct 2024. For more information about writing a blog see the blog contribution guidelines. |
Hello @matthyx 👋 1.32 Docs Shadow here. Does this enhancement work planned for 1.32 require any new docs or modifications to existing docs? Also, take a look at Documenting for a release to get yourself familiarize with the docs requirement for the release. |
Hello, @matthyx 👋 1.32 Docs Shadow here. This is just a reminder to open a placeholder PR against dev-1.32 branch in the k/website repo for this (steps available here) for this KEP if it requires new or modifications to existing docs: The deadline for this is Thursday, Oct 24 at 18:00 PDT. Thanks! 🚀 |
Hey again @matthyx 👋 v1.32 Enhancements team here, Just checking in as we approach code freeze at 02:00 UTC Friday 8th November 2024 / 19:00 PDT Thursday 7th November 2024 . Here's where this enhancement currently stands:
For this enhancement, it looks like the following PRs are open and need to be merged before code freeze: Additionally, please let me know if there are any other PRs in k/k not listed in the description or not linked with this GitHub issue that we should track for this KEP, so that we can maintain accurate status. The status of this enhancement is marked as If you anticipate missing code freeze, you can file an exception request in advance. Thank you! |
Hello @matthyx ! This is a reminder to author your placeholder feature blog post! To opt-in, let us know and open a Feature Blog placeholder PR against the website repository by 30th Oct 2024. For more information about writing a blog see the blog contribution guidelines. Please feel free to reach out if you have any questions! |
hi @rashansmith I don't think we're going to have a blog post for this alpha feature |
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: