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.
- SIG API Machinery
- SIG Architecture
- SIG Cluster Lifecycle
- Regular WG Meeting (please join [email protected] or [email protected] to access the notes): Tuesdays at 08:30 PT (Pacific Time) (weekly). Convert to your timezone.
- Weekly Mentorship Office Hours - Come ask questions and get help: Tuesdays at 10:00 PT (Pacific Time) (weekly). Convert to your timezone.
- Michael Taufen (@mtaufen), Google
- Leigh Capili (@stealthybox), Weaveworks
- Slack: #wg-component-standard
- Mailing list
- Open Community Issues/PRs
- GitHub Teams:
- @kubernetes/wg-component-standard - Component Standard Discussion
- Steering Committee Liaison: Christoph Blecker (@cblecker)
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.