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
Decouple TaintManager from NodeLifecycleController #3902
Comments
/sig apps node scheduling |
/cc @atiratree @Huang-Wei |
It was discussed at SIG Node meeting: https://docs.google.com/document/d/1Ne57gvidMEWXR70OxxnRkYquAoMpt56o75oZtg-OeBg/edit#bookmark=id.vecoal31xqar Let's track it for 1.28 to get more feedback on this as per comments at the meeting. /milestone v1.28 |
/lead-opted-in |
/label lead-opted-in |
Hello @yuanchen8911 👋, Enhancements team here. Just checking in as we approach enhancements freeze on 01:00 UTC Friday, 16th June 2023. 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 |
Thanks for checking in. The status was updated. The proposal has been reviewed extensively and is pending for final approvals. /cc @Huang-Wei @alculquicondor |
/assign @yuanchen8911 |
@yuanchen8911: 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/test-infra repository. |
/milestone 1.28 |
@alculquicondor: 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/test-infra repository. |
@yuanchen8911 it's tagged as milestone 1.28 already. You're good to go. |
Thanks, Wei. The KEP PR will need to be approved and merged by the deadline, won't it? KEP readme using the latest template has been merged into the k/enhancements repo. |
|
/stage beta |
@yuanchen8911, correct. If you plan to write up a blog, please open a separate placeholder PR for that. |
Thanks, will do it. |
Hey again @yuanchen8911👋 1.29 Enhancements team here, Just checking in as we approach code freeze at 01:00 UTC Wednesday 1st November 2023: . 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): This KEP is currently marked as Also, please let me know if there are other PRs in k/k we should be tracking for this KEP. |
Thanks, the PR is almost ready to be merged. I'll update the status once it's merged. |
Here's the blog PR (placeholder). kubernetes/website#43676 |
Hey again @yuanchen8911, 1.29 Enhancements team here. With all the implementation(code related) PRs merged as per the issue description, this enhancement is now marked as |
Thank you! |
/remove-label lead-opted-in |
Hello 👋 1.30 Enhancements Lead here, I'm closing milestone 1.29 now, /milestone clear |
Hi @alculquicondor I raise a pr to promote it to stable in 1.30. can you give a lead-opted-in label in this issue? |
/label lead-opted-in |
/remove-label lead-opted-in Actually, we recommend at least 2 releases in beta before graduation. |
@alculquicondor: 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/test-infra repository. |
Hello @alculquicondor, with your previous message, I assume that I should remove this enhancement from this release. Right? |
Yes |
/milestone clear |
Hi @yuanchen8911 This feature is not GA now. Why it is closed as completed? |
/reopen |
@alculquicondor: Reopened 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/test-infra repository. |
Sorry about the mistake. Thanks, @carlory @alculquicondor ! |
Enhancement Description
taint-manager
fromNodeLifecycleController
k/enhancements
) update PR(s): KEP-3902: Decouple TaintManager from NodeLifeCycleController #3901k/k
) update PR(s): Decouple TaintManager from NodeLifeCycleController (KEP-3902) kubernetes#119208k/website
) update(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: