forked from kubernetes/community
-
Notifications
You must be signed in to change notification settings - Fork 0
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Initial WG LTS Reformation (kubernetes#7287)
* initial wg lts changes Signed-off-by: Jeremy Rickard <jeremyrrickard@gmail.com> * Rename long-term-support to lts Signed-off-by: Jeremy Rickard <jeremyrrickard@gmail.com> * Update wg-lts/charter.md Co-authored-by: Rita Zhang <rita.z.zhang@gmail.com> * Add annual report and regular working group updates to timeline Signed-off-by: Jeremy Rickard <jeremyrrickard@gmail.com> * Update to address comments Signed-off-by: Jeremy Rickard <jeremyrrickard@gmail.com> * Address review comments Signed-off-by: Jeremy Rickard <jeremyrrickard@gmail.com> * Apply code review comment Signed-off-by: Jeremy Rickard <jeremyrrickard@gmail.com> * Add sig security to charter Signed-off-by: Jeremy Rickard <jeremyrrickard@gmail.com> * Update sigs.yaml Co-authored-by: Christoph Blecker <admin@toph.ca> * Regenerate README after sigs.yaml update Signed-off-by: Jeremy Rickard <jeremyrrickard@gmail.com> --------- Signed-off-by: Jeremy Rickard <jeremyrrickard@gmail.com> Co-authored-by: Rita Zhang <rita.z.zhang@gmail.com> Co-authored-by: Christoph Blecker <admin@toph.ca>
- Loading branch information
3 people
authored
Jul 17, 2023
1 parent
e3d9cf2
commit 0a3d25d
Showing
12 changed files
with
220 additions
and
0 deletions.
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
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,40 @@ | ||
| <!--- | ||
| 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 | ||
| ---> | ||
| # LTS Working Group | ||
|
|
||
| The working group is organized with the goal of developing a better understanding of what "Long Term Support" might mean for Kubernetes, those who support Kubernetes, and end users. The working group will investigate changes the Kubernetes project could make related to the better understanding of what long term support might mean. The working group will also determine the feasibility, benefits, **cost**, and prerequisites of any such changes. | ||
|
|
||
| ## Stakeholder SIGs | ||
| * [SIG Architecture](/sig-architecture) | ||
| * [SIG Cluster Lifecycle](/sig-cluster-lifecycle) | ||
| * [SIG K8s Infra](/sig-k8s-infra) | ||
| * [SIG Release](/sig-release) | ||
| * [SIG Security](/sig-security) | ||
| * [SIG Testing](/sig-testing) | ||
|
|
||
| ## Meetings | ||
| *Joining the [mailing list](TBD) for the group will typically add invites for the following meetings to your calendar.* | ||
| * Regular WG Meeting: [TBDs at TBD PT (Pacific Time)](TBD) (biweekly). [Convert to your timezone](http://www.thetimezoneconverter.com/?t=TBD&tz=PT%20%28Pacific%20Time%29). | ||
| * [Meeting notes and Agenda](TBD). | ||
| * [Meeting recordings](TBD). | ||
|
|
||
| ## Organizers | ||
|
|
||
| * Jeremy Rickard (**[@jeremyrickard](https://github.com/jeremyrickard)**), Microsoft | ||
| * Jordan Liggitt (**[@liggitt](https://github.com/liggitt)**), Google | ||
| * Micah Hausler (**[@micahhausler](https://github.com/micahhausler)**), Amazon | ||
|
|
||
| ## Contact | ||
| - Slack: [#wg-lts](https://kubernetes.slack.com/messages/wg-lts) | ||
| - [Mailing list](TBD) | ||
| - [Open Community Issues/PRs](https://github.com/kubernetes/community/labels/wg%2Flts) | ||
| - Steering Committee Liaison: TBD (**[@TBD](https://github.com/TBD)**) | ||
| <!-- BEGIN CUSTOM CONTENT --> | ||
|
|
||
| <!-- END CUSTOM CONTENT --> |
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,99 @@ | ||
| # WG Long Term Support | ||
|
|
||
| This charter adheres to the conventions described in the [Kubernetes Charter README] | ||
| and uses the Roles and Organization Management outlined in [sig-governance]. | ||
|
|
||
| [sig-governance]: https://github.com/kubernetes/community/blob/master/committee-steering/governance/sig-governance.md | ||
| [Kubernetes Charter README]: https://github.com/kubernetes/community/blob/master/committee-steering/governance/README.md | ||
|
|
||
| ## Scope | ||
|
|
||
| The Long Term Support Working Group (WG LTS) is organized with the goal of developing a better understanding what "Long Term Support" might mean for Kubernetes, those who support Kubernetes, and end users, as well as to investigate changes the Kubernetes project could make related to long term support. The working group will also determine feasibility, benefits, **costs**, and prerequisites of such changes. | ||
|
|
||
| In the first phase of the working group, we will collect information related to the needs and wants regarding support periods from end-users and people supporting Kubernetes. This will be accomplished by reaching out to users and cluster operators (e.g., through surveys) in order to gain a better understanding, including, but not restricted to: | ||
|
|
||
| * in-use versions (in the form of a user/vendor survey) and reasons for remaining on those versions | ||
| * constraints on deployment and upgrade patterns / timelines (e.g. edge deployments, regulated industries, retail, etc) | ||
| * expected/required support periods from users/vendors | ||
| * core Kubernetes dependencies and their support periods | ||
| * support periods of other components required to run Kubernetes clusters (OS, network, storage, etc) | ||
| * what users/vendors are currently doing to support releases past community support End Of Life (EOL) | ||
| * what do users/vendors do with EOL clusters today? what would they do if EOL was extended by N months/years? | ||
|
|
||
| With this information, we will investigate changes the Kubernetes project could make to address these needs. A non-exhaustive set of changes to investigate include: | ||
| * lengthening support period for all minor versions | ||
| * lengthening support period for specific minor versions | ||
| * applying security fixes to release branches past current EOL without cutting additional patch releases | ||
| * applying security and "critical" fixes to release branches past current EOL without cutting additional patch releases | ||
| * expanding supported skew | ||
| * improving supported upgrade patterns for clusters at EOL | ||
|
|
||
| ### In Scope | ||
|
|
||
| - Collecting input to better define long term support with regard to Kubernetes releases. This could include: | ||
| * What is a supported release? | ||
| * Number of community supported branches. | ||
| * Duration of community support per supported branch. | ||
| - Working with vendors and other community members to identify ongoing efforts to help end users beyond current community support and identify opportunities for reuse of prior work. | ||
| - Creating and prioritizing a list of areas that require investments to improve long term supportability. This could include: | ||
| * Upgrade path considerations. | ||
| * Costs of Kubernetes releases in terms of: | ||
| * Infrastructure | ||
| * People | ||
| - Initiating and driving cross-SIG changes related to long term support. | ||
| - Identifing ways to that vendors and other community members can better support Kubernetes releases. | ||
|
|
||
| ### Out of scope | ||
|
|
||
| - The lifecycle of projects outside of the Kubernetes org. | ||
| - Designing and executing on changes clearly falling into individual SIG | ||
| responsibilities. This is a working group, no code implementation is the responsibility of this Working Group. | ||
| - Technical and end-user support: The WG may make recommendations | ||
| around support to those responsible for relevant code and responsible | ||
| for the release engineering operations and automation, but does not | ||
| own code itself. | ||
|
|
||
| ## Special Powers | ||
|
|
||
| None | ||
|
|
||
| ## Stakeholders | ||
|
|
||
| Any changes identified by this working group will require involvement and investment from the following SIGS: | ||
|
|
||
| - SIG Architecture | ||
| High-level input on requirements. | ||
| - SIG Cluster Lifecycle | ||
| Input on cluster upgrade mechanics. | ||
| - SIG K8s Infra | ||
| Input on infrastructure costs related to increased support period(s). | ||
| - SIG Release | ||
| Input on maintaining older branches and additional releases. | ||
| - SIG Security | ||
| Input on vulnerability management process and audits for additional releases. | ||
| - SIG Testing | ||
| Input on testing impacts related to upgrades and longer test periods. | ||
|
|
||
| Improvements identified will likely involve every SIG, but the list above are identified as the primary stakeholders. | ||
|
|
||
| ## Deliverables | ||
|
|
||
| The artifacts the group is supposed to deliver include: | ||
| - Survey results better describing Kubernetes version use patterns, deployment constraints, and upgrade patterns. | ||
| - Recommend changes Kubernetes SIGs can make that will provide broad benefits in a sustainable/affordable way. This would likely take the form of one or more KEPs. | ||
| - Recommend ways users/vendors who want to maximize Kubernetes support can consume Kubernetes | ||
|
|
||
| Any changes identified will be owned by corresponding SIGs. | ||
|
|
||
| ## Roles and Organization Management | ||
|
|
||
| This working group adheres to the Roles and Organization Management outlined in | ||
| [sig-governance] and opts-in to updates and modifications to [sig-governance]. | ||
|
|
||
| [sig-governance]: https://github.com/kubernetes/community/blob/master/committee-steering/governance/sig-governance.md | ||
|
|
||
| ## Timelines and Disbanding | ||
|
|
||
| The exact timeline for this working group is hard to define at this time. If we are unable to define a common long term support definition for Kubernetes, we will disband the working group. If we are unable to define improvements related to an agreed upon definition, we will also disband the working group. In order to evaluate our progress toward the working group goals, we will provide periodic updates to the stakeholder SIGs and committees at least every six months, in addition to a working group annual report. | ||
|
|
||
| Additionally, if the working group determines that the Kubernetes project does not have sufficient resources, nor commmitments for future resources to support relevant proposed changes, the working group will also disband. |