WIP: Introduce Node Lifecycle WG #8396
+248
−0
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
|
|
@@ -3697,6 +3697,46 @@ workinggroups: | |
| liaison: | ||
| github: saschagrunert | ||
| name: Sascha Grunert | ||
| - dir: wg-node-lifecycle | ||
| name: Node Lifecycle | ||
| mission_statement: > | ||
| Explore and improve node and pod lifecycle in Kubernetes. This should result in | ||
| better node drain/maintenance support and better pod disruption/termination. It | ||
| should also improve node and pod autoscaling, better application migration and | ||
| availability, load balancing, de/scheduling, node shutdown, cloud provider integrations, | ||
| and support other new scenarios and integrations. | ||
|
|
||
| charter_link: charter.md | ||
| stakeholder_sigs: | ||
| - Apps | ||
| - Architecture | ||
| - Autoscaling | ||
| - CLI | ||
| - Cloud Provider | ||
| - Cluster Lifecycle | ||
| - Network | ||
| - Node | ||
atiratree marked this conversation as resolved.
Show resolved
Hide resolved
|
||
| - Scheduling | ||
|
There was a problem hiding this comment. Dont we need to add other infra SIGs like storage as stakeholders too ? There was a problem hiding this comment. +1 added, this list is not final and we will have conversations with each SIG after the KubeCon if they want to be part of this WG There was a problem hiding this comment. I know SIG Storage is impacted as well, I am just not sure how much cooperation is needed. |
||
| - Storage | ||
| label: node-lifecycle | ||
| leadership: | ||
| chairs: | ||
| - github: atiratree | ||
| name: Filip Křepinský | ||
| company: Red Hat | ||
| email: [email protected] | ||
| meetings: | ||
| - description: WG Node Lifecycle Weekly Meeting | ||
| day: TBD | ||
| time: TBD | ||
| tz: TBD | ||
| frequency: weekly | ||
| contact: | ||
| slack: wg-node-lifecycle | ||
| mailing_list: https://groups.google.com/a/kubernetes.io/g/wg-node-lifecycle | ||
| liaison: | ||
| github: TBD | ||
| name: TBD | ||
| - dir: wg-policy | ||
| name: Policy | ||
| mission_statement: > | ||
|
|
||
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,8 @@ | ||
| # See the OWNERS docs at https://go.k8s.io/owners | ||
|
|
||
| reviewers: | ||
| - wg-node-lifecycle-leads | ||
| approvers: | ||
| - wg-node-lifecycle-leads | ||
| labels: | ||
| - wg/node-lifecycle |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,42 @@ | ||
| <!--- | ||
| This is an autogenerated file! | ||
|
|
||
| Please do not edit this file directly, but instead make changes to the | ||
| sigs.yaml file in the project root. | ||
|
|
||
| To understand how this file is generated, see https://git.k8s.io/community/generator/README.md | ||
| ---> | ||
| # Node Lifecycle Working Group | ||
|
|
||
| Explore and improve node and pod lifecycle in Kubernetes. This should result in better node drain/maintenance support and better pod disruption/termination. It should also improve node and pod autoscaling, better application migration and availability, load balancing, de/scheduling, node shutdown, cloud provider integrations, and support other new scenarios and integrations. | ||
|
|
||
| The [charter](charter.md) defines the scope and governance of the Node Lifecycle Working Group. | ||
|
|
||
| ## Stakeholder SIGs | ||
| * [SIG Apps](/sig-apps) | ||
| * [SIG Architecture](/sig-architecture) | ||
| * [SIG Autoscaling](/sig-autoscaling) | ||
| * [SIG CLI](/sig-cli) | ||
| * [SIG Cloud Provider](/sig-cloud-provider) | ||
| * [SIG Cluster Lifecycle](/sig-cluster-lifecycle) | ||
| * [SIG Network](/sig-network) | ||
| * [SIG Node](/sig-node) | ||
atiratree marked this conversation as resolved.
Show resolved
Hide resolved
|
||
| * [SIG Scheduling](/sig-scheduling) | ||
| * [SIG Storage](/sig-storage) | ||
|
|
||
| ## Meetings | ||
| *Joining the [mailing list](https://groups.google.com/a/kubernetes.io/g/wg-node-lifecycle) for the group will typically add invites for the following meetings to your calendar.* | ||
| * WG Node Lifecycle Weekly Meeting: [TBDs at TBD TBD]() (weekly). [Convert to your timezone](http://www.thetimezoneconverter.com/?t=TBD&tz=TBD). | ||
|
|
||
| ## Organizers | ||
|
|
||
| * Filip Křepinský (**[@atiratree](https://github.com/atiratree)**), Red Hat | ||
|
|
||
| ## Contact | ||
| - Slack: [#wg-node-lifecycle](https://kubernetes.slack.com/messages/wg-node-lifecycle) | ||
| - [Mailing list](https://groups.google.com/a/kubernetes.io/g/wg-node-lifecycle) | ||
| - [Open Community Issues/PRs](https://github.com/kubernetes/community/labels/wg%2Fnode-lifecycle) | ||
| - Steering Committee Liaison: TBD (**[@TBD](https://github.com/TBD)**) | ||
| <!-- BEGIN CUSTOM CONTENT --> | ||
|
|
||
| <!-- END CUSTOM CONTENT --> | ||
Oops, something went wrong.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
You are missing network, that owns loadbalancing, endpoints, ... and already has serious problems because of known issues like https://docs.google.com/document/d/1t25jgO_-LRHhjRXf4KJ5xY_t8BZYdapv7MDAxVGY6R8/edit?tab=t.0#heading=h.i4lwa7rdng7y
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
+1 added the SIG and the doc link, we need to address the loadbalancing and endpoints as well