Decouple TaintManager from NodeLifecycleController

[yuanchen8911]

Enhancement Description

• One-line enhancement description (can be used as a release note): Decouple taint-manager from NodeLifecycleController
• Kubernetes Enhancement Proposal: https://github.com/kubernetes/enhancements/blob/master/keps/sig-scheduling/3902-decoupled-taint-manager/README.md
• Discussion Link: Decouple Taint-based Pod Eviction from Node LifeCycle Controller  kubernetes#115779
• Primary contact (assignee): @yuanchen8911
• Responsible SIGs: sig-scheduling
• Enhancement target (which target equals to which milestone):
  • Alpha release target (x.y): Since there are no new API changes, we can skip Alpha and go to Beta directly.
  • Beta release target (x.y): 1.29
  • Stable release target (x.y): 1.33?
• Beta
  • KEP (k/enhancements) update PR(s): KEP-3902: Decouple TaintManager from NodeLifeCycleController #3901
  • Code (k/k) update PR(s): Decouple TaintManager from NodeLifeCycleController (KEP-3902) kubernetes#119208
  • Docs (k/website) update(s):
    • [WIP] Docs for Decoupled TaintManager from NodeLifeCycleController (KEP-3902) website#41970
    • Docs for Decoupled TaintManager from NodeLifeCycleController (KEP-3902) website#43555
    • Blog: Add a blog post about decoupled taint eviction controller website#43676
• Stable
  • KEP (k/enhancements) update PR(s): [1.33] promote KEP-3902 to stable #4392
  • Code (k/k) update PR(s):
  • Docs (k/website) update(s):

Please keep this description up to date. This will help the Enhancement Team to track the evolution of the enhancement efficiently.

[yuanchen8911]

/sig apps node scheduling

[yuanchen8911]

/cc @ddebroy @atosatto @ravisantoshgudimetla

[yuanchen8911]

/cc @atiratree @Huang-Wei

[SergeyKanzhelev]

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

[alculquicondor]

/lead-opted-in

[alculquicondor]

/label lead-opted-in

[salehsedghpour]

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 beta for 1.28 (correct me, if otherwise)

Here's where this enhancement currently stands:

• KEP readme using the latest template has been merged into the k/enhancements repo.
• KEP status is marked as implementable for latest-milestone: 1.28
• KEP readme has a updated detailed test plan section filled out
• KEP readme has up to date graduation criteria
• KEP has a production readiness review that has been completed and merged into k/enhancements.

For this KEP, we would just need to update the following:

• Address questions inside the Production Readiness Review Questionnaire.
• Ensure that the PRs are merged.

The status of this enhancement is marked as at risk. Please keep the issue description up-to-date with appropriate stages as well. Thank you!

[yuanchen8911]

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 alpha for 1.28 (correct me, if otherwise)

Here's where this enhancement currently stands:

• KEP readme using the latest template has been merged into the k/enhancements repo.
• KEP status is marked as implementable for latest-milestone: 1.28
• KEP readme has a updated detailed test plan section filled out
• KEP readme has up to date graduation criteria
• KEP has a production readiness review that has been completed and merged into k/enhancements.

For this KEP, we would just need to update the following:

• Address questions inside the Production Readiness Review Questionnaire.
• Ensure that the PRs are merged.

The status of this enhancement is marked as at risk. Please keep the issue description up-to-date with appropriate stages as well. Thank you!

Thanks for checking in. The status was updated. The proposal has been reviewed extensively and is pending for final approvals. /cc @Huang-Wei @alculquicondor

[yuanchen8911]

/assign @yuanchen8911

[k8s-ci-robot]

@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:

/milestone 1.28

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.

[alculquicondor]

/milestone 1.28

[k8s-ci-robot]

@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:

/milestone 1.28

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.

[Huang-Wei]

@yuanchen8911 it's tagged as milestone 1.28 already. You're good to go.

[yuanchen8911]

@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.

[k8s-triage-robot]

The Kubernetes project currently lacks enough contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue as fresh with /remove-lifecycle stale
• Close this issue with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

[carlory]

/remove-lifecycle stale

[kannon92]

Reading this, I'm not sure this needs to be in tracked sig-node KEPs for 1.32. If you need reviewers from sig-node, please let us know!

[alculquicondor]

There is an open PR #4392

@yuanchen8911, can you update the description?

[carlory]

@alculquicondor Can you give me a lead-opted-in label?

[alculquicondor]

/lead-opted-in

[alculquicondor]

/label lead-opted-in

[soltysh]

/milestone v1.32
/stage stable

[dipesh-rawat]

Hello @yuanchen8911 @carlory 👋, 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 stable for v1.32 (correct me, if otherwise)

Here's where this enhancement currently stands:

• KEP readme using the latest template has been merged into the k/enhancements repo.
• KEP status is marked as implementable for latest-milestone: v1.32.
• KEP readme has up-to-date graduation criteria
• KEP has a production readiness review that has been completed and merged into k/enhancements. (For more information on the PRR process, check here). If your production readiness review is not completed yet, please make sure to fill the production readiness questionnaire in your KEP by the PRR Freeze deadline on Thursday 3rd October 2024 so that the PRR team has enough time to review your KEP.

For this KEP, we would just need to update the following:

• Update kep.yaml to mention latest-milestone: v1.32 and stable: "v1.32"
• Complete the PRR review process for stable stage and merge it into k/enhancements.

It looks like #4392 will address most of these issues.

• Get [1.33] promote KEP-3902 to stable #4392 merged before the enhancements freeze.

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.

If you anticipate missing enhancements freeze, you can file an exception request in advance. Thank you!

[dipesh-rawat]

Hi @yuanchen8911 @carlory 👋, v1.32 Enhancements team here.

Just a quick friendly reminder as we approach the enhancements freeze later this week, at 02:00 UTC Friday 11th October 2024 / 19:00 PDT Thursday 10th October 2024.

The current status of this enhancement is marked as at risk for enhancement freeze. There are a few requirements mentioned in the comment #3902 (comment) that still need to be completed.

It looks like PR #4392 will address most of these issues. The PR #4392 needs to be merged before the enhancements freeze.

If you anticipate missing enhancements freeze, you can file an exception request in advance. Thank you!

[tjons]

Hello 👋, v1.32 Enhancements team here.

Unfortunately, this enhancement did not meet requirements for enhancements freeze.

If you still wish to progress this enhancement in 1.32, 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!

[tjons]

/milestone clear

[k8s-triage-robot]

The Kubernetes project currently lacks enough contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue as fresh with /remove-lifecycle stale
• Close this issue with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

[carlory]

/remove-lifecycle stale

[dipesh-rawat]

Hello 👋, 1.33 Enhancements Lead here.

If you'd like to work on this enhancement in v1.33, please have the SIG lead opt-in by adding the lead-opted-in label, which ensures it gets added to the tracking board. Also, please set the milestone to v1.33 using /milestone v1.33.
Thanks!

/remove-label lead-opted-in