The Architecture SIG maintains and evolves the design principles of Kubernetes, and provides a consistent body of expertise necessary to ensure architectural consistency over time.
The charter defines the scope and governance of the Architecture Special Interest Group.
- Regular SIG Meeting: Thursdays at 19:00 UTC (weekly). Convert to your timezone.
The Chairs of the SIG run operations and processes governing the SIG.
- Brian Grant (@bgrant0607), Google
- Jaice Singer DuMars (@jdumars), Google
- Matt Farina (@mattfarina), Samsung SDS
The following subprojects are owned by sig-architecture:
- architecture-and-api-governance
- Description: Described below
- Owners:
- https://raw.githubusercontent.com/kubernetes/community/master/contributors/design-proposals/architecture/OWNERS
- https://raw.githubusercontent.com/kubernetes-sigs/architecture-tracking/master/OWNERS
- https://raw.githubusercontent.com/kubernetes/api/master/OWNERS
- https://raw.githubusercontent.com/kubernetes/kubernetes/master/staging/src/k8s.io/api/OWNERS
- conformance-definition
- kep-adoption-and-reviews
- Description: Described below
- Owners:
- code-organization
- Description: Described below
- Owners:
- https://raw.githubusercontent.com/kubernetes/contrib/master/OWNERS
- https://raw.githubusercontent.com/kubernetes/utils/master/OWNERS
- https://raw.githubusercontent.com/kubernetes/kubernetes/master/vendor/OWNERS
- https://raw.githubusercontent.com/kubernetes/kubernetes/master/third_party/OWNERS
- https://raw.githubusercontent.com/kubernetes/kubernetes/master/staging/OWNERS
- steering
- Description: Placeholder until sigs.yaml supports committees as first-class groups. These repos are owned by the kubernetes steering committee, which is a wholly separate entity from SIG Architecture
- Owners:
The below teams can be mentioned on issues and PRs in order to get attention from the right people. Note that the links to display team membership will only work if you are a member of the org.
| Team Name | Details | Description |
|---|---|---|
| @kubernetes/sig-architecture-api-reviews | link | API Changes and Reviews |
| @kubernetes/sig-architecture-bugs | link | Bug Triage and Troubleshooting |
| @kubernetes/sig-architecture-feature-requests | link | Feature Requests |
| @kubernetes/sig-architecture-misc-use-only-as-a-last-resort | link | General Discussion |
| @kubernetes/sig-architecture-pr-reviews | link | PR Reviews |
| @kubernetes/sig-architecture-proposals | link | Design Proposals |
| @kubernetes/sig-architecture-test-failures | link | Test Failures and Triage |
Establishing and documenting design principles, documenting and evolving the system architecture, reviewing, curating, and documenting new extension patterns
Establishing and documenting conventions for system and user-facing APIs, define and operate the APl review process, final API implementation consistency validation, co-own top-level API directories with API machinery; maintaining, evolving, and enforcing the deprecation policy
- Kubernetes Design and Architecture
- Design principles
- API conventions
- API Review process
- Deprecation policy
Please see the Design documentation and API Reviews tracking boards to follow the work of this sub-project. Please reach out to folks in the OWNERS file if you are interested in joining this effort.
Reviewing, approving, and driving changes to the conformance test suite; reviewing, guiding, and creating new conformance profiles
Please see the Conformance Test Review tracking board to follow the work for this sub-project. Please reach out to folks in the OWNERS file if you are interested in joining this effort. There is a lot of overlap with the Kubernetes Software Conformance Working Group with this sub project as well. The github group cncf-conformance-wg enumerates the folks on this working group. Look for the area/conformance label in the kubernetes repositories to mark issues and PRs
Develop and drive technical enhancement review process
Please see the KEP Tracking board to follow the work of this sub-project. Please reach out to folks in the OWNERS file if you are interested in joining this effort.
Overall code organization, including github repositories and branching methodology, top-level and pkg OWNERS of kubernetes/kubernetes, vendoring
Please reach out to folks in the OWNERS file if you are interested in joining this effort.