Dissolving WG Component Standard

[Michael Taufen]

Dear Kubernetes community and WG Component Standard,

We have not found replacement chairs for WG Component Standard, and the group has not met or been particularly active since July 2020 (link). Therefore, we are planning to move forward with dissolving WG Component Standard. Our next step will be to update the community repo to reflect this status.

While the group has been inactive for some time, there is still worthwhile work remaining, particularly:

• Stewardship of the component-base repo, which hosts common code reused by many K8s components.

• Encouraging components to use Kubernetes-style config files instead of command-line flags for their configuration (a.k.a. ComponentConfig).

Responsibility for these areas, and other potential work outlined in the founding KEP, now returns to our stakeholder SIGs (Architecture, Cluster Lifecycle, and API Machinery). 

Specifically:

• Overall responsibility for the component-base repo returns to SIG-Architecture. The OWNERS file for component-base was recently updated to reflect this. We also took a first pass at identifying more specific owners of subdirectories to reduce noise for SIG-Architecture. If you believe there is a mistake or misalignment in currently assigned ownership, please feel free to open a PR with your proposed corrections.

• While the ComponentConfig pattern conceptually sits between the Cluster Lifecycle and API Machinery, it falls to the SIGs that directly own each component to drive their own migrations. For instance, SIG-Node is responsible for Kubelet's config file. ComponentConfig files have a number of benefits over command-line flags, and we encourage the SIGs to consider these when ranking the priority of their migrations.

We want to give A HUGE thank you to all the community members who contributed to WGCS, whose contributions include:

• Refactoring common code for flag handling, config, logs, and metrics to the component-base repo, that was previously spread out across k/k.

• Continued progress on migrating components to ComponentConfig, thanks to the efforts of many new contributors who helped out as part of our mentorship drive.

• Implementing strict decoders for ComponentConfig types.

• Adding test coverage for ComponentConfig types.

• Progress toward generic ComponentConfig in controller-runtime.

• Welcoming new members to the community via contributor onboarding and mentorship.

• KubeCon talks in 2019 and 2020.

Leigh and I are still here in the community, sometimes working on similar projects, sometimes things completely different. We look forward to seeing you all around for years to come.

Best to all,

Mike Taufen and Leigh Capili, WG Component Standard Chairs

--

Michael Taufen

Google SWE

[Michael Taufen]

[Aaron Crickenberger]

Do we need to hear an ack from Stakeholder SIGs or Steering Committee before proceeding, or do folks feel like this fits https://github.com/kubernetes/community/blob/master/committee-steering/governance/wg-governance.md#disbandment-process-description sufficiently well to move forward without any +1's?

- aaron

[Davanum Srinivas]

+1 to wrap this up. Thanks a ton Mike and Leigh for all the work and leadership!

-- Dims

--
You received this message because you are subscribed to the Google Groups "Kubernetes developer/contributor discussion" group.
To unsubscribe from this group and stop receiving emails from it, send an email to kubernetes-de...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/kubernetes-dev/650752e1-bb45-43de-b984-fd8865d76308n%40googlegroups.com.

--

Davanum Srinivas :: https://twitter.com/dims