community/wg-component-standard
Michael Taufen 24dda029b3 wg-component-standard: sttts is stepping down
sttts is stepping down as wg chair.
Update the readme and metadata to reflect this change.

Thank you sttts for all your work in the WG!

https://groups.google.com/g/kubernetes-wg-component-standard/c/Q_NwH25fqWw/m/ba9tuSwXCAAJ
2020-07-27 09:31:12 -07:00
..
README.md wg-component-standard: sttts is stepping down 2020-07-27 09:31:12 -07:00

README.md

Component Standard Working Group

Develop a standard foundation (philosophy and libraries) for core Kubernetes components to build on top of. Areas to standardize include configuration (flags, ComponentConfig APIs, ...), status endpoints (healthz, configz, ...), integration points (delegated authn/z, ...), and logging. Details are outlined in KEP 0032: https://github.com/kubernetes/enhancements/blob/master/keps/sig-cluster-lifecycle/wgs/0032-create-a-k8s-io-component-repo.md.

Stakeholder SIGs

  • SIG API Machinery
  • SIG Architecture
  • SIG Cluster Lifecycle

Meetings

Organizers

Contact

Issues

Issues are opened in kubernetes/kubernetes or the appropriate project/component repo with the wg/component-standard label.
To apply this label to an issue using Prow, leave a comment containing /wg component-standard on its own line.

kubernetes/component-base is an automated staging repository managed from the ./staging directory in kubernetes/kubernetes. Issues are not currently looked at on this repo.

Adding issues to the project board is helpful.
The wg/component-standard label is used in other org's repos such as kubernetes-sigs/kubebuilder meaning you can't link them easily in the Project Board.
For repos outside of the kubernetes org, You can add(+) a note with links to the issues on the Project Board.