Skip to content

Blog with KEP-3902 in 1.34#51560

Merged
k8s-ci-robot merged 1 commit intokubernetes:mainfrom
carlory:KEP3902BLOG
Aug 21, 2025
Merged

Blog with KEP-3902 in 1.34#51560
k8s-ci-robot merged 1 commit intokubernetes:mainfrom
carlory:KEP3902BLOG

Conversation

@carlory
Copy link
Copy Markdown
Member

@carlory carlory commented Jul 9, 2025

Description

Issue

Closes: #

@k8s-ci-robot k8s-ci-robot added cncf-cla: yes Indicates the PR's author has signed the CNCF CLA. size/XS Denotes a PR that changes 0-9 lines, ignoring generated files. labels Jul 9, 2025
@netlify
Copy link
Copy Markdown

netlify bot commented Jul 9, 2025

Pull request preview available for checking

Built without sensitive environment variables

Name Link
🔨 Latest commit c9ac4be
🔍 Latest deploy log https://app.netlify.com/projects/kubernetes-io-main-staging/deploys/689e9d22403e010009541e19
😎 Deploy Preview https://deploy-preview-51560--kubernetes-io-main-staging.netlify.app
📱 Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.

To edit notification comments on pull requests, go to your Netlify project configuration.

@graz-dev
Copy link
Copy Markdown
Contributor

graz-dev commented Jul 9, 2025

/area blog

@k8s-ci-robot k8s-ci-robot added the area/blog Issues or PRs related to the Kubernetes Blog subproject label Jul 9, 2025
@dipesh-rawat
Copy link
Copy Markdown
Member

Hi @atiratree @carlory 👋 v1.34 Communications team here,

@atiratree as author of #45268, I'd like you to be a writing buddy for @carlory on this PR.

Please:

  • Review this PR, paying attention to the guidelines and review hints
  • Update your own PR based on any best practices you identify that should be applied
  • Remember to be compassionate with your fellow article author

@aibarbetta
Copy link
Copy Markdown
Member

/sig release

@k8s-ci-robot k8s-ci-robot added the sig/release Categorizes an issue or PR as relevant to SIG Release. label Jul 13, 2025
@graz-dev
Copy link
Copy Markdown
Contributor

Hi @carlory 👋 -- this is Graz from the v1.34 Communications Team!

Just a friendly reminder that we are approaching the feature blog "ready for review" deadline: Friday 8th August 2025. We ask you to have the blog in non-draft state, and all write-up to be complete.

If you have any questions or need help, please don't hesitate to reach out to me or any of the Communications Team members. We are here to help you!

@k8s-ci-robot k8s-ci-robot added language/en Issues or PRs related to English language size/M Denotes a PR that changes 30-99 lines, ignoring generated files. and removed size/XS Denotes a PR that changes 0-9 lines, ignoring generated files. labels Aug 6, 2025
@carlory carlory changed the title [placeholder] Blog with KEP-3902 in 1.34 Blog with KEP-3902 in 1.34 Aug 6, 2025
@carlory
Copy link
Copy Markdown
Member Author

carlory commented Aug 6, 2025

@graz-dev updated.

@aibarbetta
Copy link
Copy Markdown
Member

@carlory is this ready for review?
@graz-dev since the writing buddy is from a KEP that was removed from the v1.34 milestone, can you cover the review?

@carlory
Copy link
Copy Markdown
Member Author

carlory commented Aug 7, 2025

@aibarbetta Yes, it is ready for review.

@@ -0,0 +1,40 @@
---
layout: blog
title: "Kubernetes v1.34: Decoupling taint-manager from node-lifecycle-controller Moves to GA"
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
title: "Kubernetes v1.34: Decoupling taint-manager from node-lifecycle-controller Moves to GA"
title: "Kubernetes v1.34: Decoupling TaintManager from NodeLifecycleController Moves to GA"

In other post we used to mention these components as CamelCase: https://kubernetes.io/blog/2023/12/13/kubernetes-v1-29-release/#node-lifecycle-separated-from-taint-management-sig-scheduling-https-github-com-kubernetes-community-tree-master-sig-scheduling

But in other blog posts we mentioned it as reported here: https://kubernetes.io/blog/2023/12/19/kubernetes-1-29-taint-eviction-controller/

@lmktfy in your opinion what is the right one?

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'd write "node lifecycle controller" (no quotes). Use English by default; we make exceptions for some things, but usually not controllers.

(It's different if the controller name is a proper noun, eg Karpenter).

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

For a title, how about this

Kubernetes v1.34: Decoupled Taint Manager Is Now Stable

?

Copy link
Copy Markdown
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

updated with Kubernetes v1.34: Decoupled Taint Manager Is Now Stable

The feature gate `SeparateTaintEvictionController` has been promoted to GA in this release.
Users can optionally disable taint-based eviction by setting `--controllers=-taint-eviction-controller`
in kube-controller-manager.

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I suggest to add some more datails to this paragraph just to keep it informative without just linking to other resources. That's an example of what I would add:

This enhancement separates the responsibility of managing node health and pod eviction into two distinct components. Previously, the node-lifecycle-controller handled both marking nodes as unhealthy with NoExecute taints and evicting pods from them. Now, a dedicated taint-eviction-controller manages the eviction process, while the node-lifecycle-controller focuses solely on applying taints. This decoupling improves maintainability and offers greater flexibility, allowing administrators to implement custom eviction strategies tailored to specific workloads, such as stateful applications that require more graceful handling of node failures to prevent data loss.

That's just a reference of what I mean, and it's written just by reading the KEP content so it can be not 100% correct.

Copy link
Copy Markdown
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

updated.


## How can I learn more?

For more details, refer to the [KEP](http://kep.k8s.io/3902) and [Blog](/blog/2023/12/19/taint-eviction-controller).
Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
For more details, refer to the [KEP](http://kep.k8s.io/3902) and [Blog](/blog/2023/12/19/taint-eviction-controller).
For more details, refer to the [KEP](http://kep.k8s.io/3902) and to the beta announcement article: [Kubernetes 1.29: Decoupling taint-manager from node-lifecycle-controller](/blog/2023/12/19/kubernetes-1-29-taint-eviction-controller/).

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

BTW if we want to fix the title of the previous article to omit the - characters, we just can (in this PR, even). No need for a special approval process.

Copy link
Copy Markdown
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

updated.

Signed-off-by: carlory <baofa.fan@daocloud.io>
Copy link
Copy Markdown
Member

@lmktfy lmktfy left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

/lgtm
/approve

Baofa Fan (DaoCloud)
---

This enhancement separates the responsibility of managing node lifecycle and pod eviction into two distinct components.
Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

nit: (could fix after a merge)

As a side note, I think actually that page (Scheduling, Preemption and Eviction) should change to mention the taint eviction controller a little more.

@k8s-ci-robot k8s-ci-robot added the lgtm "Looks good to me", indicates that a PR is ready to be merged. label Aug 21, 2025
@k8s-ci-robot
Copy link
Copy Markdown
Contributor

LGTM label has been added.

DetailsGit tree hash: 98f5cfd2abb5b11690932013d631db1944e7b137

@k8s-ci-robot
Copy link
Copy Markdown
Contributor

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: lmktfy

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Details Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@k8s-ci-robot k8s-ci-robot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Aug 21, 2025
@k8s-ci-robot k8s-ci-robot merged commit 2a0dbcb into kubernetes:main Aug 21, 2025
6 checks passed
@graz-dev graz-dev mentioned this pull request Sep 2, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

approved Indicates a PR has been approved by an approver from all required OWNERS files. area/blog Issues or PRs related to the Kubernetes Blog subproject cncf-cla: yes Indicates the PR's author has signed the CNCF CLA. language/en Issues or PRs related to English language lgtm "Looks good to me", indicates that a PR is ready to be merged. sig/release Categorizes an issue or PR as relevant to SIG Release. size/M Denotes a PR that changes 30-99 lines, ignoring generated files.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

6 participants