-
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
Deprecate & remove Kubelet RunOnce mode #4580
Comments
/sig node |
/label lead-opted-in |
/stage alpha |
Hello @HirazawaUi 👋, Enhancements team here. Just checking in as we approach enhancements freeze on 02:00 UTC Friday 14th June 2024 / 19:00 PDT Thursday 13th June 2024.. This enhancement is targeting stage 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 If you anticipate missing enhancements freeze, you can file an exception request in advance. Thank you! |
With #4581 merged, we can mark this KEP as |
Hello there @HirazawaUi 👋 from the v1.31 Communications Team! 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 |
Hello @HirazawaUi 👋, 1.31 Docs Shadow here. Does this enhancement work planned for 1.31 require any new docs or modification to existing docs? If so, please follows the steps here to open a PR against dev-1.31 branch in the k/website repo. This PR can be just a placeholder at this time and must be created before Thursday June 27, 2024 18:00 PDT. Also, take a look at Documenting for a release to get yourself familiarised with the docs requirement for the release. Thank you! |
Hey again @HirazawaUi 👋, 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:
Regarding this enhancement, it appears that there are currently no open pull requests in the k/k repository related to it. For this KEP, we would need to do the following:
If you anticipate missing code freeze, you can file an exception request in advance. The status of this enhancement is marked as |
Hey again @HirazawaUi 👋, 1.31 Enhancements team here, Just a quick friendly reminder as we approach code freeze in about 2 days, at 02:00 UTC Wednesday 24th July 2024 / 19:00 PDT Tuesday 23rd July 2024. The current status of this enhancement is marked as at risk for code freeze. A few requirements mentioned in the comment #4580 (comment) still need to be completed:
If you anticipate missing code freeze, you can file an exception request in advance. |
@ArkaSaha30 I'm pushing it forward, but we still have some issues that are unresolved. |
Since we are very close to the Code Freeze_(02:00 UTC Wednesday 24th July 2024 / 19:00 PDT Tuesday 23rd July 2024.)_ I would request you to file an exception request if you anticipate it can make it to 1.31. |
I'm guessing kubernetes/kubernetes#125649 is the only PR that we need to track for this KEP. This PR has got an approval and is waiting for conflicts to be fixed. @HirazawaUi: Please let us know if there is anything else. |
Hello @HirazawaUi 👋 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. (Your PR kubernetes/kubernetes#125649 has a merge conflict). 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 |
/close |
@HirazawaUi: Closing this 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. |
@HirazawaUi Do we not need this KEP for the deprecation? Should someone else take up this KEP for the next cycle? |
Enhancement Description
k/enhancements
) update PR(s):k/k
) update PR(s): Deprecate Kubelet RunOnce mode kubernetes#125649k/website
) update PR(s): [WIP] Document deprecation & likely future removal of kubelet RunOnce mode website#46934Please 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: