This charter adheres to the conventions described in the Kubernetes Charter README and uses the Roles and Organization Management outlined in sig-governance.
SIG API Machinery is responsible for the development and enhancement of Kubernetes cluster control plane. The scope covers API server, persistence layer (etcd), controller manager, cloud controller manager, CustomResourceDefinition and webhooks.
All aspects of
- API server
- API registration and discovery
- Generic API CRUD semantics
- Admission control
- Encoding/decoding
- Conversion
- Defaulting
- Persistence layer (etcd)
- OpenAPI
- The informer libraries
- CustomResourceDefinition
- Webhooks
- Garbage collection
- Namespace lifecycle
- Client libraries
Client library releases
The contents of individual APIs are owned by SIG Architecture
This sig follows adheres to the Roles and Organization Management outlined in sig-governance and opts-in to updates and modifications to sig-governance.
Technical leads seeded by legacy SIG chairs from existing subproject owners
N/A
SIG delegates subproject approval to Technical Leads. See Subproject creation - Option 1.