Introduce Node Lifecycle WG by atiratree · Pull Request #8396 · kubernetes/community

atiratree · 2025-03-24T12:17:05Z

No description provided.

atiratree · 2025-03-24T13:48:19Z

/hold

rthallisey · 2025-03-24T14:04:33Z

Looks like I'm not a member of kubernetes org anymore. I was a few years back, but didn't keep up with contributions recently. You can remove me as a lead and I can reapply after some contributions to this WG.

atiratree · 2025-03-24T14:59:20Z

We have had impactful conversations with Ryan about this group and its goals. He has experience with cluster maintenance and I look forward to his participation in the WG.

marquiz · 2025-03-25T17:09:04Z

/cc

mrunalp · 2025-06-05T21:39:41Z

+1

SergeyKanzhelev · 2025-06-06T00:55:24Z

+1 from SIG Node. SIG Node sponsors this WG with the understanding that the group will concentrate on both - shaping and driving existing KEPs to progress thru stages as well as collecting and evaluating requirements and deciding on priorities for introducing new KEPs.

SergeyKanzhelev

/lgtm

jsafrane · 2025-06-06T09:10:56Z

lgtm from sig-storage

soltysh

with my sig-apps hat I'll add +1 from sig-apps

See my various comments, also I'm still missing ACK from sig network and sig scheduling

soltysh · 2025-06-09T09:03:02Z

+* Humble Chirammal (**[@humblec](https://github.com/humblec)**), VMware
+* Lucy Sweet (**[@intUnderflow](https://github.com/intUnderflow)**), Uber
+* Krzysztof Wilczyński (**[@kwilczynski](https://github.com/kwilczynski)**), Independent
+* Ryan Hallisey (**[@rthallisey](https://github.com/rthallisey)**), NVIDIA


Do we really need that many leads for this WG? Isn't it sufficient to have one per representing company, ensuring they cover all the related sigs?

We either have represantation of different SIGs or different companies, so I am not seeing any duplicate role at this moment. Perhaps we could trim this list later according to these folks' activity and continued interest?

Being a lead is a certain responsibility. It goes beyond "is interested in the topic". But I'm okay with letting you figure out among yourself who is really showing up consistently to keep the WG moving and then perhaps do some pruning.

same concern but overall lgtm

/approve

For Steering.

followup in #8748

soltysh · 2025-06-09T09:03:53Z

+    mailing_list: https://groups.google.com/a/kubernetes.io/g/wg-node-lifecycle
+    liaison:
+      github: TBD
+      name: TBD


@kubernetes/steering-committee we'll need to figure this out prior to merge.

They can provisionally put me.
I'm happy to and based on load + election timing that makes sense as you mentioned elsewhere.
If anyone objects we can update it.

Thanks for covering the liaison role @BenTheElder! Added.

macsko · 2025-06-09T09:49:01Z

+1 from SIG Scheduling

aojea · 2025-06-09T10:48:40Z


 The following [working groups][working-group-definition] are sponsored by sig-network:
 * [WG Device Management](/wg-device-management)
+* [WG Node Lifecycle](/wg-node-lifecycle)


+1 from SIG Network

BenTheElder · 2025-06-18T22:04:49Z

I think we finally have all SIG +1s now?
cc @kubernetes/steering-committee

This group will have a lot to do :-)
+1, thanks for pulling this together.

soltysh

/lgtm
/approve

/hold
to get sufficient majority from steering

pohly · 2025-06-23T13:27:54Z

+* Humble Chirammal (**[@humblec](https://github.com/humblec)**), VMware
+* Lucy Sweet (**[@intUnderflow](https://github.com/intUnderflow)**), Uber
+* Krzysztof Wilczyński (**[@kwilczynski](https://github.com/kwilczynski)**), Independent
+* Ryan Hallisey (**[@rthallisey](https://github.com/rthallisey)**), NVIDIA


Being a lead is a certain responsibility. It goes beyond "is interested in the topic". But I'm okay with letting you figure out among yourself who is really showing up consistently to keep the WG moving and then perhaps do some pruning.

pohly · 2025-06-23T13:33:26Z

+## Timelines and Disbanding
+
+The working group will disband once the features and core APIs defined in the following
+KEPs/Features have reached a stable state (GA) and ongoing maintenance ownership is established


There are no "following KEPs/Features"... so your work is already done? 😛

You probably had this in a different order initially and lost them during some reshuffling. I think this refers to the features under "Prioritization" now?

Right, updated!

pohly · 2025-06-24T09:39:19Z

/approve

For Steering.

https://github.com/kubernetes/community/pull/8396/files#r2161652316 should better get resolved before merging. Also, needs a rebase...

Co-authored-by: Ryan Hallisey <rhallisey@nvidia.com>

atiratree · 2025-06-24T10:23:53Z

Updated and rebased. Thanks everyone!

k8s-ci-robot · 2025-06-24T14:06:37Z

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: atiratree, pacoxu, pohly, soltysh

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:

~~OWNERS~~ [pacoxu,pohly,soltysh]

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

soltysh · 2025-06-24T15:23:04Z

With 4 steering members +1-ing (Paco, Patrick, Ben and myself) this is good to go as is based on the rules.

/hold cancel

evrardjp

A few extra comments for the sake of history/documentation. I just hope someone will read them and have them in mind when we'll produce solutions.

evrardjp · 2025-06-25T06:16:15Z

+- Consider improving the pod lifecycle of DaemonSets and static pods during a node maintenance.
+- Explore the cloud provider use cases and how they can hook into the node lifecycle. So that the
+  users can use the same APIs or configurations across the board.
+- Migrate users of the eviction based kubectl-like drain (kubectl, cluster autoscaler, karpenter,


I am a bit sad that kured was removed here, while it was in the initial comments on a previous issue.

I would like to adapt kured to this framework at least.

@evrardjp no worries! This list is not supposed to be exhaustive. We will properly explore the migration topic when the time comes.

FYI, kured is still present in https://github.com/kubernetes/community/blob/master/wg-node-lifecycle/charter.md#relevant-projects

evrardjp · 2025-06-25T06:18:53Z

+- Explore a unified way of draining the nodes and managing node maintenance by introducing new APIs
+  and extending the current ones. This includes exploring extension to or interactions with the Node
+  object.
+- Analyze the node lifecycle, the Node API, and possible interactions. We want to explore augmenting


I think we could have been more specific here. For example, analyse the possibility to set new conditions onto nodes.

The WG charter does not replace a proper KEP; it only indicates the direction in which we would like to proceed. So we will even explore options that are not explicitly listed here.

evrardjp · 2025-06-25T06:23:09Z

+We expect to provide reference implementations of the new APIs including but not limited to
+controllers (kube-controller-manager), API validation, integration with existing core components and
+extension points for the ecosystem. This should be accompanied by E2E / Conformance tests.
+


CLI might be too broad. Nevertheless we talk about the kubectl above and will also further analyze it in our KEPs.

k8s-ci-robot added cncf-cla: yes Indicates the PR's author has signed the CNCF CLA. area/community-management area/slack-management Issues or PRs related to the Slack Management subproject labels Mar 24, 2025

k8s-ci-robot requested review from ahg-g and ardaguclu March 24, 2025 12:17

github-project-automation Bot added this to SIG Scheduling Mar 24, 2025

github-project-automation Bot moved this to Needs Triage in SIG Scheduling Mar 24, 2025

atiratree changed the title ~~Introduce Node Lifecycle WG~~ WIP: Introduce Node Lifecycle WG Mar 24, 2025

k8s-ci-robot added the do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. label Mar 24, 2025

k8s-ci-robot added the do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. label Mar 24, 2025

atiratree force-pushed the wg-node-lifecycle branch from 75e1096 to a19a192 Compare March 24, 2025 14:47

k8s-ci-robot removed the do-not-merge/invalid-owners-file Indicates that a PR should not merge because it has an invalid OWNERS file in it. label Mar 24, 2025

k8s-ci-robot requested a review from marquiz March 25, 2025 17:09

atiratree force-pushed the wg-node-lifecycle branch from a19a192 to 2d6ac13 Compare March 25, 2025 17:52

SergeyKanzhelev reviewed Jun 4, 2025

View reviewed changes

Comment thread wg-node-lifecycle/charter.md

atiratree force-pushed the wg-node-lifecycle branch from cf8dbfb to 3aed2af Compare June 5, 2025 18:11

SergeyKanzhelev reviewed Jun 6, 2025

View reviewed changes

k8s-ci-robot assigned SergeyKanzhelev Jun 6, 2025

k8s-ci-robot added the lgtm "Looks good to me", indicates that a PR is ready to be merged. label Jun 6, 2025

soltysh reviewed Jun 9, 2025

View reviewed changes

aojea reviewed Jun 9, 2025

View reviewed changes

Comment thread wg-node-lifecycle/charter.md

aojea reviewed Jun 9, 2025

View reviewed changes

Comment thread wg-node-lifecycle/charter.md

aojea reviewed Jun 9, 2025

View reviewed changes

Comment thread wg-node-lifecycle/charter.md Outdated

aojea reviewed Jun 9, 2025

View reviewed changes

atiratree force-pushed the wg-node-lifecycle branch from 3aed2af to 39e3bde Compare June 10, 2025 10:13

k8s-ci-robot removed the lgtm "Looks good to me", indicates that a PR is ready to be merged. label Jun 10, 2025

humblec reviewed Jun 12, 2025

View reviewed changes

Comment thread sigs.yaml

intUnderflow reviewed Jun 15, 2025

View reviewed changes

Comment thread sigs.yaml Outdated

soltysh approved these changes Jun 19, 2025

View reviewed changes

pohly reviewed Jun 23, 2025

View reviewed changes

Introduce Node Lifecycle WG

149f04c

Co-authored-by: Ryan Hallisey <rhallisey@nvidia.com>

evrardjp reviewed Jun 25, 2025

View reviewed changes

This was referenced Jun 26, 2025

introduce wg/node-lifecycle label and update OWNER_ALIASES kubernetes/test-infra#35037

Merged

add a mailing list for WG Node Lifecycle kubernetes/k8s.io#8259

Merged

atiratree mentioned this pull request Jan 20, 2026

update WG Node Lifecycle leads #8748

Merged

Conversation

atiratree commented Mar 24, 2025

Uh oh!

atiratree commented Mar 24, 2025

Uh oh!

rthallisey commented Mar 24, 2025

Uh oh!

atiratree commented Mar 24, 2025

Uh oh!

marquiz commented Mar 25, 2025

Uh oh!

Uh oh!

mrunalp commented Jun 5, 2025

Uh oh!

SergeyKanzhelev commented Jun 6, 2025

Uh oh!

SergeyKanzhelev left a comment

Choose a reason for hiding this comment

Uh oh!

jsafrane commented Jun 6, 2025

Uh oh!

soltysh left a comment

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

macsko commented Jun 9, 2025 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Uh oh!

Uh oh!

BenTheElder commented Jun 18, 2025

Uh oh!

soltysh left a comment

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

pohly commented Jun 24, 2025

Uh oh!

atiratree commented Jun 24, 2025

Uh oh!

k8s-ci-robot commented Jun 24, 2025

Uh oh!

soltysh commented Jun 24, 2025

Uh oh!

evrardjp left a comment • edited Loading Uh oh! There was an error while loading. Please reload this page.

macsko commented Jun 9, 2025 •

edited

Loading

evrardjp left a comment •

edited

Loading