Architecture Special Interest Group

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.

Meetings

Joining the mailing list for the group will typically add invites for the following meetings to your calendar.

Enhancements Subproject Meeting: Thursdays at 10:00 PT (Pacific Time) (biweekly). Convert to your timezone.
- Meeting notes and Agenda.
- Meeting recordings.
Production Readiness Office Hours: Wednesdays at 12:00 PT (Pacific Time) (biweekly). Convert to your timezone.
- Meeting notes and Agenda.
- Meeting recordings.
Regular SIG Meeting: Thursdays at 11:00 PT (Pacific Time) (biweekly). Convert to your timezone.
- Meeting notes and Agenda.
- Meeting recordings.
code organization Office Hours: Thursdays at 14:00 PT (Pacific Time) (biweekly). Convert to your timezone.
- Meeting notes and Agenda.
- Meeting recordings.
conformance office Hours: Wednesdays at 18:00 UTC (First Wednesday of the month). Convert to your timezone.
- Meeting notes and Agenda.
- Meeting recordings.

Leadership

Chairs

The Chairs of the SIG run operations and processes governing the SIG.

Derek Carr (@derekwaynecarr), Red Hat
Davanum Srinivas (@dims), Amazon
John Belamaric (@johnbelamaric), Google

Contact

Slack: #sig-architecture
Mailing list
Open Community Issues/PRs
GitHub Teams:
- @kubernetes/sig-architecture-api-reviews - API Changes and Reviews
- @kubernetes/sig-architecture-bugs - Bug Triage and Troubleshooting
- @kubernetes/sig-architecture-feature-requests - Feature Requests
- @kubernetes/sig-architecture-misc-use-only-as-a-last-resort - General Discussion
- @kubernetes/sig-architecture-pr-reviews - PR Reviews
- @kubernetes/sig-architecture-proposals - Design Proposals
- @kubernetes/sig-architecture-test-failures - Test Failures and Triage
Steering Committee Liaison: Benjamin Elder (@BenTheElder)

Working Groups

The following working groups are sponsored by sig-architecture:

Subprojects

The following subprojects are owned by sig-architecture:

apisnoop

Snooping on the Kubernetes OpenAPI communications

Owners:
- kubernetes-sigs/apisnoop

architecture-and-api-governance

Described below

Owners:

maintainer-tools

Tooling based on Deep Learning tools to help maintainers to maintain the Kubernetes project.

Owners:
- kubernetes-sigs/maintainer-tools/heads/main

production-readiness

Described below

Owners:
- kubernetes/community/sig-architecture
Contact:
- Slack: #prod-readiness

wg-ai-conformance

Proposals and discussions for the AI Conformance Working Group

Owners:
- kubernetes-sigs/wg-ai-conformance

wg-device-management

Contains prototype code for future work driven by WG Device Management

Owners:
- kubernetes-sigs/wg-device-management
Contact:
- Slack: #wg-device-management

wg-serving

Owners:
- kubernetes-sigs/wg-serving

Details about SIG-Architecture sub-projects

Architecture and API Governance

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

Please see the API Reviews 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.

Enhancement Proposals

Kubernetes Enhancement proposals (KEPs) are used to propose and communicate changes to sub-projects of SIG-Architecture. Following the KEP process is mandatory for all enhancements since Kubernetes 1.14 release.

Conformance Definition

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.

Code Organization

Overall code organization, including github repositories and branching methodology, top-level and pkg OWNERS of kubernetes/kubernetes, vendoring

Please see the Code Organization 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. Look for the area/code-organization label in the kubernetes repositories to mark issues and PRs. We also use area/dependency label as well issues and PRs.

Production Readiness

Defining and documenting the processes for ensuring production readiness of new and promoted features, as well as producing tooling to enforce those processes.