The Kpt governance model is modeled after Kubernetes. In particular, we leverage the same hierarchy of steering committee, SIGs, subprojects, working groups that Kubernetes does to facilitiate engagement with the greater ecosystem. We plan to refine this over time as the number of contributors grow. As an example, we don't plan to record all sig meetings at the start but may over time as it becomes valuable for interested parties who miss the meetings. If something is not defined here, it is expected that we will inherit the Kubernetes equivalent.
The Kpt Steering Committee is the governing body for the Kpt project Please reach out to us on slack or attend one of the SIG meetings to bring up anything you'd like to discuss. We actively partcipate in the SIGs as well as Office Hours
| Name | Profile |
|---|---|
| Chris Sosa | @selfmanagingresource |
| Brian Grant | @bgrant0607 |
| Justin Santa Barbara | @justinsb |
| John Belamaric | @johnbelamaric |
Covers leveraging Config as Data to customize and automate configuration at scale. This is the largest SIG in Kpt that spans most of its surface area including incubation for apply config as data to new use cases.
- Brian Grant ( @bgrant0607)
- Chris Sosa (@selfmanagingresource)
Everything not covered by another sub-project including porch, fn render, etc
Owns the SDK that enables our Config as Data experience
- Yuwen Ma ( @yuwenma)
Focused on making it easy to leverage Config as Data with application workloads
- Chris Sosa (@selfmanagingresource)
Focused on making it easy to automate deployments through GitOps. Owns the APIs and tools that are part of the Config Sync repository