Blog with KEP-3902 in 1.34#51560
Conversation
✅ Pull request preview available for checkingBuilt without sensitive environment variables
To edit notification comments on pull requests, go to your Netlify project configuration. |
|
/area blog |
|
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:
|
|
/sig release |
|
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! |
|
@graz-dev updated. |
content/en/blog/_posts/XXXX-XX-XX-taint-eviction-controller-moves-ga.md
Outdated
Show resolved
Hide resolved
content/en/blog/_posts/XXXX-XX-XX-taint-eviction-controller-moves-ga.md
Outdated
Show resolved
Hide resolved
content/en/blog/_posts/XXXX-XX-XX-taint-eviction-controller-moves-ga.md
Outdated
Show resolved
Hide resolved
|
@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" | |||
There was a problem hiding this comment.
| 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?
There was a problem hiding this comment.
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).
There was a problem hiding this comment.
For a title, how about this
Kubernetes v1.34: Decoupled Taint Manager Is Now Stable
?
There was a problem hiding this comment.
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. | ||
|
|
There was a problem hiding this comment.
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.
content/en/blog/_posts/XXXX-XX-XX-taint-eviction-controller-moves-ga.md
Outdated
Show resolved
Hide resolved
|
|
||
| ## 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). |
There was a problem hiding this comment.
| 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/). |
There was a problem hiding this comment.
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.
content/en/blog/_posts/XXXX-XX-XX-taint-eviction-controller-moves-ga.md
Outdated
Show resolved
Hide resolved
Signed-off-by: carlory <baofa.fan@daocloud.io>
| Baofa Fan (DaoCloud) | ||
| --- | ||
|
|
||
| This enhancement separates the responsibility of managing node lifecycle and pod eviction into two distinct components. |
There was a problem hiding this comment.
nit: (could fix after a merge)
- I recommend hyperlinking to https://kubernetes.io/docs/concepts/scheduling-eviction/
As a side note, I think actually that page (Scheduling, Preemption and Eviction) should change to mention the taint eviction controller a little more.
|
LGTM label has been added. DetailsGit tree hash: 98f5cfd2abb5b11690932013d631db1944e7b137 |
|
[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 DetailsNeeds approval from an approver in each of these files:
Approvers can indicate their approval by writing |
Description
Issue
Closes: #