Skip to content

Introduce Node Lifecycle WG #8396

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.

Sign up for GitHub

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

Jump to bottom
Open
wants to merge 1 commit into
base: master
Choose a base branch
from
Open

Introduce Node Lifecycle WG #8396

wants to merge 1 commit into from
+351 −0

Conversation

atiratree
Copy link
Member

No description provided.

@k8s-ci-robot 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 k8s-ci-robot requested review from ahg-g and ardaguclu March 24, 2025 12:17
@k8s-ci-robot k8s-ci-robot added committee/steering Denotes an issue or PR intended to be handled by the steering committee. sig/apps Categorizes an issue or PR as relevant to SIG Apps. sig/architecture Categorizes an issue or PR as relevant to SIG Architecture. size/L Denotes a PR that changes 100-499 lines, ignoring generated files. sig/autoscaling Categorizes an issue or PR as relevant to SIG Autoscaling. sig/cli Categorizes an issue or PR as relevant to SIG CLI. sig/cloud-provider Categorizes an issue or PR as relevant to SIG Cloud Provider. sig/cluster-lifecycle Categorizes an issue or PR as relevant to SIG Cluster Lifecycle. sig/contributor-experience Categorizes an issue or PR as relevant to SIG Contributor Experience. do-not-merge/invalid-owners-file Indicates that a PR should not merge because it has an invalid OWNERS file in it. sig/node Categorizes an issue or PR as relevant to SIG Node. sig/scheduling Categorizes an issue or PR as relevant to SIG Scheduling. labels Mar 24, 2025
@github-project-automation github-project-automation bot moved this to Needs Triage in SIG Scheduling Mar 24, 2025
@atiratree atiratree changed the title Introduce Node Lifecycle WG WIP: Introduce Node Lifecycle WG Mar 24, 2025
@k8s-ci-robot 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
@atiratree
Copy link
Member Author

/hold

@k8s-ci-robot 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
@rthallisey
Copy link

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.

@k8s-ci-robot 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
@atiratree
Copy link
Member Author

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
Copy link
Contributor

marquiz commented Mar 25, 2025

/cc

@k8s-ci-robot k8s-ci-robot requested a review from marquiz March 25, 2025 17:09
@ardaguclu
Copy link
Member

+1 from SIG CLI based on the discussion in sig-cli bi-weekly meeting happened on 16th of April 2025.

@gjtempleton
Copy link
Member

+1 from SIG Autoscaling

SergeyKanzhelev
SergeyKanzhelev reviewed Jun 4, 2025
View reviewed changes
SergeyKanzhelev
SergeyKanzhelev reviewed Jun 4, 2025
View reviewed changes
@atiratree atiratree force-pushed the wg-node-lifecycle branch from cf8dbfb to 3aed2af Compare June 5, 2025 18:11
@mrunalp
Copy link
Contributor

mrunalp commented Jun 5, 2025

+1

@SergeyKanzhelev
Copy link
Member

+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
SergeyKanzhelev reviewed Jun 6, 2025
View reviewed changes
Copy link
Member

@SergeyKanzhelev SergeyKanzhelev left a comment

Choose a reason for hiding this comment

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

/lgtm

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

jsafrane commented Jun 6, 2025

lgtm from sig-storage

soltysh
soltysh reviewed Jun 9, 2025
View reviewed changes
Copy link
Contributor

@soltysh soltysh left a comment

Choose a reason for hiding this comment

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

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

wg-node-lifecycle/README.md
* 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
Copy link
Contributor

Choose a reason for hiding this comment

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

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?

Copy link
Member Author

Choose a reason for hiding this comment

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

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?

sigs.yaml Outdated
mailing_list: https://groups.google.com/a/kubernetes.io/g/wg-node-lifecycle
liaison:
github: TBD
name: TBD
Copy link
Contributor

Choose a reason for hiding this comment

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

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

Copy link
Member

Choose a reason for hiding this comment

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

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.

Copy link
Member Author

Choose a reason for hiding this comment

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

Thanks for covering the liaison role @BenTheElder! Added.

@macsko
Copy link
Member

macsko commented Jun 9, 2025 •
edited
Loading

+1 from SIG Scheduling

aojea
aojea reviewed Jun 9, 2025
View reviewed changes
aojea
aojea reviewed Jun 9, 2025
View reviewed changes
aojea
aojea reviewed Jun 9, 2025
View reviewed changes
aojea
aojea reviewed Jun 9, 2025
View reviewed changes
sig-network/README.md
@@ -70,6 +70,7 @@ subprojects, and resolve cross-subproject technical issues and decisions.

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

Choose a reason for hiding this comment

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

+1 from SIG Network

@atiratree atiratree force-pushed the wg-node-lifecycle branch from 3aed2af to 39e3bde Compare June 10, 2025 10:13
@k8s-ci-robot k8s-ci-robot removed the lgtm "Looks good to me", indicates that a PR is ready to be merged. label Jun 10, 2025
humblec
humblec reviewed Jun 12, 2025
View reviewed changes
intUnderflow
intUnderflow reviewed Jun 15, 2025
View reviewed changes
@atiratree atiratree force-pushed the wg-node-lifecycle branch from 39e3bde to f920fdf Compare June 16, 2025 08:04
@atiratree @rthallisey
Introduce Node Lifecycle WG
ddcdc26 
Co-authored-by: Ryan Hallisey <[email protected]>
@atiratree atiratree force-pushed the wg-node-lifecycle branch from f920fdf to ddcdc26 Compare June 16, 2025 08:23
@BenTheElder
Copy link
Member

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
soltysh approved these changes Jun 19, 2025
View reviewed changes
Copy link
Contributor

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

/hold
to get sufficient majority from steering

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

[APPROVALNOTIFIER] This PR is APPROVED

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

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

The pull request process is described here

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 Jun 19, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers

@humblec humblec humblec left review comments

@elmiko elmiko elmiko left review comments

@aojea aojea aojea left review comments

@gnufied gnufied gnufied left review comments

@BenTheElder BenTheElder BenTheElder left review comments

@ajaysundark ajaysundark ajaysundark left review comments

@jsafrane jsafrane jsafrane left review comments

@wangzhen127 wangzhen127 wangzhen127 left review comments

@rthallisey rthallisey rthallisey left review comments

@janetkuo janetkuo janetkuo left review comments

@Karthik-K-N Karthik-K-N Karthik-K-N left review comments

@pohly pohly pohly left review comments

@kannon92 kannon92 kannon92 left review comments

@ordovicia ordovicia ordovicia left review comments

@haircommander haircommander haircommander left review comments

@JoelSpeed JoelSpeed JoelSpeed left review comments

@johnbelamaric johnbelamaric johnbelamaric left review comments

@SergeyKanzhelev SergeyKanzhelev SergeyKanzhelev left review comments

@intUnderflow intUnderflow intUnderflow left review comments

@ivelichkovich ivelichkovich ivelichkovich left review comments

@adrianchiris adrianchiris adrianchiris left review comments

@soltysh soltysh soltysh approved these changes

@ahg-g ahg-g Awaiting requested review from ahg-g

@ardaguclu ardaguclu Awaiting requested review from ardaguclu

@marquiz marquiz Awaiting requested review from marquiz

@cartermckinnon cartermckinnon Awaiting requested review from cartermckinnon

@hakman hakman Awaiting requested review from hakman

@AndrewSirenko AndrewSirenko Awaiting requested review from AndrewSirenko

@jackfrancis jackfrancis Awaiting requested review from jackfrancis

Assignees

@soltysh soltysh

@SergeyKanzhelev SergeyKanzhelev

Labels
approved Indicates a PR has been approved by an approver from all required OWNERS files. area/community-management area/slack-management Issues or PRs related to the Slack Management subproject cncf-cla: yes Indicates the PR's author has signed the CNCF CLA. committee/steering Denotes an issue or PR intended to be handled by the steering committee. do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. lgtm "Looks good to me", indicates that a PR is ready to be merged. sig/apps Categorizes an issue or PR as relevant to SIG Apps. sig/architecture Categorizes an issue or PR as relevant to SIG Architecture. sig/autoscaling Categorizes an issue or PR as relevant to SIG Autoscaling. sig/cli Categorizes an issue or PR as relevant to SIG CLI. sig/cloud-provider Categorizes an issue or PR as relevant to SIG Cloud Provider. sig/cluster-lifecycle Categorizes an issue or PR as relevant to SIG Cluster Lifecycle. sig/contributor-experience Categorizes an issue or PR as relevant to SIG Contributor Experience. sig/network Categorizes an issue or PR as relevant to SIG Network. sig/node Categorizes an issue or PR as relevant to SIG Node. sig/scheduling Categorizes an issue or PR as relevant to SIG Scheduling. sig/storage Categorizes an issue or PR as relevant to SIG Storage. size/L Denotes a PR that changes 100-499 lines, ignoring generated files.
Projects
SIG Scheduling
Status: Needs Triage
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.