Kubernetes Contributors – Special Interest Groups (SIGs)

Community: SIG API Machinery

Mon, 01 Jan 0001 00:00:00 +0000

API Machinery Special Interest Group

Covers all aspects of API server, API registration and discovery, generic API CRUD semantics, admission control, encoding/decoding, conversion, defaulting, persistence layer (etcd), OpenAPI, CustomResourceDefinition, garbage collection, and client libraries.

The charter defines the scope and governance of the API Machinery Special Interest Group.

Meetings

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

Declarative APIs and Linters Meeting: Tuesdays at 9:00 PT (Pacific Time) (biweekly). Convert to your timezone .
- Meeting notes and Agenda .
- Meeting recordings .
Kubebuilder Meeting: Thursdays at 11:00 PT (Pacific Time) (biweekly). Convert to your timezone .
- Meeting notes and Agenda .
- Meeting recordings .
Regular SIG Meeting: Wednesdays at 11:00 PT (Pacific Time) (biweekly). Convert to your timezone .
- Meeting notes and Agenda .
- Meeting recordings .

Leadership

Chairs

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

David Eads (@deads2k ), Red Hat
Federico Bongiovanni (@fedebongio ), Google

Technical Leads

The Technical Leads of the SIG establish new subprojects, decommission existing subprojects, and resolve cross-subproject technical issues and decisions.

David Eads (@deads2k ), Red Hat
Joe Betz (@jpbetz ), Google
Stefan Schimanski (@sttts ), Upbound

Contact

Slack: #sig-api-machinery
Mailing list
Open Community Issues/PRs
GitHub Teams:
- @kubernetes/sig-api-machinery-api-reviews - API Changes and Reviews (API Machinery APIs, NOT all APIs)
- @kubernetes/sig-api-machinery-bugs - Bug Triage and Troubleshooting
- @kubernetes/sig-api-machinery-feature-requests - Feature Requests
- @kubernetes/sig-api-machinery-misc - General Discussion
- @kubernetes/sig-api-machinery-pr-reviews - PR Reviews
- @kubernetes/sig-api-machinery-proposals - Design Proposals
- @kubernetes/sig-api-machinery-test-failures - Test Failures and Triage
Steering Committee Liaison: Sascha Grunert (@saschagrunert )

Subprojects

The following subprojects are owned by sig-api-machinery:

server-sdk

universal-machinery

Owners:
- kubernetes/apimachinery
- kubernetes/kubernetes/staging/src/k8s.io/apimachinery

yaml

Owners:
- kubernetes-sigs/yaml

Additional links

YouTube Playlist - find meeting recordings here

Community: SIG Apps

Mon, 01 Jan 0001 00:00:00 +0000

Apps Special Interest Group

Covers deploying and operating applications in Kubernetes. We focus on the developer and devops experience of running applications in Kubernetes. We discuss how to define and run apps in Kubernetes, demo relevant tools and projects, and discuss areas of friction that can lead to suggesting improvements or feature requests.

The charter defines the scope and governance of the Apps Special Interest Group.

Meetings

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

Regular SIG Meeting (calendar ) : Mondays at 9:00 PT (Pacific Time) (biweekly). Convert to your timezone .
- Meeting notes and Agenda .
- Meeting recordings .
Subproject Agent Sandbox Meeting (calendar ) : Mondays at 9:00 PT (Pacific Time) (biweekly). Convert to your timezone .
- Meeting notes and Agenda .
- Meeting recordings .

Leadership

Chairs

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

Janet Kuo (@janetkuo ), Google
Kenneth Owens (@kow3ns ), Snowflake
Maciej Szulik (@soltysh ), Defense Unicorns

Technical Leads

The Technical Leads of the SIG establish new subprojects, decommission existing subprojects, and resolve cross-subproject technical issues and decisions.

Janet Kuo (@janetkuo ), Google
Kenneth Owens (@kow3ns ), Snowflake
Maciej Szulik (@soltysh ), Defense Unicorns

Emeritus Leads

Matt Farina (@mattfarina )
Adnan Abdulhussein (@prydonius )

Contact

Slack: #sig-apps
Mailing list
Open Community Issues/PRs
GitHub Teams:
- @kubernetes/sig-apps-api-reviews - API Changes and Reviews
- @kubernetes/sig-apps-bugs - Bug Triage and Troubleshooting
- @kubernetes/sig-apps-feature-requests - Feature Requests
- @kubernetes/sig-apps-misc - General Discussion
- @kubernetes/sig-apps-pr-reviews - PR Reviews
- @kubernetes/sig-apps-proposals - Design Proposals
- @kubernetes/sig-apps-test-failures - Test Failures and Triage
Steering Committee Liaison: Antonio Ojea (@aojea )

Working Groups

The following working groups are sponsored by sig-apps:

Subprojects

The following subprojects are owned by sig-apps:

agent-devops

Owners:
- kubernetes-sigs/devops-bench
- kubernetes-sigs/kube-agents

agent-sandbox

Easy management of isolated, stateful, singleton workloads, ideal for use cases like AI agent runtimes

Owners:
- kubernetes-sigs/agent-sandbox
Contact:
- Slack: #agent-sandbox

application

Application metadata descriptor CRD

Owners:
- kubernetes-sigs/application
- kubernetes-sigs/mcp-lifecycle-operator

examples

Owners:
- kubernetes/examples

execution-hook

Owners:
- kubernetes-sigs/execution-hook

kjob

Owners:
- kubernetes-sigs/kjob

kompose

Owners:
- kubernetes/kompose
Contact:
- Slack: #kompose

workloads-api

The core workloads API, which is composed of the CronJob, DaemonSet, Deployment, Job, ReplicaSet, ReplicationController, PodDisruptionBudget and StatefulSet kinds

Owners:

Goals

Discuss running and defining applications in Kubernetes (e.g., APIs, SDKs, Controllers, package management tools, etc.)
Work on improvements to the Workload API
Suggest Kubernetes features where we see friction
Be the voice of the people running applications in Kubernetes (developers and devops)
Help people get involved in the Kubernetes community
Show early features/demos of tools that make running apps easier

Non-goals

Do not endorse one particular ecosystem tool
Do not pick which apps to run on top of Kubernetes
Do not recommend one way to do things (e.g., picking a template language)

Helm and Charts

Helm, Charts and its other subprojects have moved to the CNCF . See Helm’s community repository for information about the Helm project.

Community: SIG Architecture

Mon, 01 Jan 0001 00:00:00 +0000

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.

AI Conformance Meeting (calendar ) : Thursdays at 10:00 PT (Pacific Time) (biweekly). Convert to your timezone .
- Meeting notes and Agenda .
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 ), NVIDIA
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:

WG Device Management

Subprojects

The following subprojects are owned by sig-architecture:

admission-policies

Mutating and Validating Admission Policies published by the Kubernetes project.

Owners:
- kubernetes-sigs/admission-policies

ai-conformance

Proposals and tests for AI Conformance

Leads:
- Janet Kuo (@janetkuo ), Google
- Mario Fahlandt (@mfahlandt ), Kubermatic GmbH
- Rita Zhang (@ritazh ), Microsoft
- Yuan Tang (@terrytangyuan ), Red Hat
Owners:
- kubernetes-sigs/ai-conformance
Contact:
- Slack: #k8s-ai-conformance

apisnoop

Snooping on the Kubernetes OpenAPI communications

Owners:
- kubernetes-sigs/apisnoop

architecture-and-api-governance

Described below

Owners:

code-organization

Described below

conformance-definition

Described below

Owners:
Contact:
- Slack: #k8s-conformance
- GitHub Teams:
  - @kubernetes/cncf-conformance-wg

enhancements

Described below

Owners:
- kubernetes/enhancements
Contact:
- Slack: #enhancements

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-device-management

Contains prototype code for future work driven by WG Device Management

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

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.

Answers to our FAQs can be found here FAQs
Full details of the KEP process can be found in KEP-1
Please follow the KEP template available at KEP Template for the enhancement proposal.
Progress of KEPs can be tracked on our github project board at Kubernetes Enhancements
Please review OWNERS to connect with enhancement chairs, approvers, and reviewers

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.

Community: SIG Auth

Mon, 01 Jan 0001 00:00:00 +0000

Auth Special Interest Group

Covers improvements to Kubernetes authorization, authentication, and cluster security policy.

“All I want is a secure system where it’s easy to do anything I want. Is that so much to ask?” - xkcd

The charter defines the scope and governance of the Auth Special Interest Group.

Meetings

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

Regular SIG Meeting: Wednesdays at 11:00 PT (Pacific Time) (biweekly, you must be signed into a free zoom account to join). Convert to your timezone .
- Meeting notes and Agenda .
- Meeting recordings .
Secrets Store CSI Meeting: Thursdays at 9:00 PT (Pacific Time) (biweekly, you must be signed into a free zoom account to join). Convert to your timezone .
- Meeting notes and Agenda .
- Meeting recordings .
Weekly Issues/PR Triage Meeting: Mondays at 9:00 PT (Pacific Time) (weekly, you must be signed into a free zoom account to join). Convert to your timezone .

Leadership

Chairs

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

Anish Ramasekar (@aramase ), Microsoft
Micah Hausler (@micahhausler ), Amazon
Rita Zhang (@ritazh ), Microsoft

Technical Leads

The Technical Leads of the SIG establish new subprojects, decommission existing subprojects, and resolve cross-subproject technical issues and decisions.

David Eads (@deads2k ), Red Hat
Mo Khan (@enj ), Microsoft
Jordan Liggitt (@liggitt ), Google

Emeritus Leads

Eric Chiang (@ericchiang )
Eric Tune (@erictune )
Mike Danese (@mikedanese )
Tim Allclair (@tallclair )

Contact

Slack: #sig-auth
Mailing list
Open Community Issues/PRs
GitHub Teams:
- @kubernetes/sig-auth-api-reviews - API Changes and Reviews
- @kubernetes/sig-auth-bugs - Bug Triage and Troubleshooting
- @kubernetes/sig-auth-feature-requests - Feature Requests
- @kubernetes/sig-auth-misc - General Discussion
- @kubernetes/sig-auth-pr-reviews - PR Reviews
- @kubernetes/sig-auth-proposals - Design Proposals
- @kubernetes/sig-auth-test-failures - Test Failures and Triage
Steering Committee Liaison: Kat Cosgrove (@katcosgrove )

Working Groups

The following working groups are sponsored by sig-auth:

WG Checkpoint Restore

Subprojects

The following subprojects are owned by sig-auth:

audit-logging

Kubernetes API support for audit logging.

Owners:

authenticators

Kubernetes API support for authentication.

Owners:

authorizers

Kubernetes API support for authorization.

Owners:

certificates

Certificates APIs and client infrastructure to support PKI.

Owners:

encryption-at-rest

API storage support for storing data encrypted at rest in etcd.

Owners:
- kubernetes/kubernetes/staging/src/k8s.io/apiserver/pkg/server/options/encryptionconfig
- kubernetes/kubernetes/staging/src/k8s.io/apiserver/pkg/storage/value

node-identity-and-isolation

Node identity management (co-owned with sig-lifecycle), and authorization restrictions for isolating workloads on separate nodes (co-owned with sig-node).

Owners:

policy-management

API validation and policies enforced during admission, such as PodSecurityPolicy. Excludes run-time policies like NetworkPolicy and Seccomp.

Owners:

secrets-store-csi-driver

Integrates secrets stores with Kubernetes via a CSI volume.

Leads:
- Anish Ramasekar (@aramase ), Microsoft
- Rita Zhang (@ritazh ), Microsoft
Owners:
- kubernetes-sigs/secrets-store-csi-driver
Contact:
- Slack: #csi-secrets-store
- Mailing List

secrets-store-sync-controller

This is a Kubernetes controller that watches for changes to a custom resource and syncs the secrets from external secrets-store as Kubernetes secret.

Leads:
- Anish Ramasekar (@aramase ), Microsoft
- Mo Khan (@enj ), Microsoft
Owners:
- kubernetes-sigs/secrets-store-sync-controller

service-accounts

Infrastructure implementing Kubernetes service account based workload identity.

Owners:

sig-auth-tools

Tooling to automate the SIG Auth project boards

Owners:
- kubernetes-sigs/sig-auth-tools

Community: SIG Autoscaling

Mon, 01 Jan 0001 00:00:00 +0000

Autoscaling Special Interest Group

Covers development and maintenance of components for automated scaling in Kubernetes. This includes automated vertical and horizontal pod autoscaling, initial resource estimation, cluster-proportional system component autoscaling, and autoscaling of Kubernetes clusters themselves.

The charter defines the scope and governance of the Autoscaling Special Interest Group.

Meetings

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

Regular SIG Meeting: Thursdays at 17:00 Poland (weekly). Convert to your timezone .
- Meeting notes and Agenda .

Leadership

Chairs

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

Jack Francis (@jackfrancis ), Microsoft
Kuba Tużnik (@towca ), Google

Technical Leads

The Technical Leads of the SIG establish new subprojects, decommission existing subprojects, and resolve cross-subproject technical issues and decisions.

Adrian Moisey (@adrianmoisey ), Independent
Omer Aplatony (@omerap12 ), Red Hat
Kuba Tużnik (@towca ), Google

Emeritus Leads

Guy Templeton (@gjtempleton )
Maciek Pytel (@maciekpytel )
Marcin Wielgus (@mwielgus )
Ray Wainman (@raywainman )

Contact

Slack: #sig-autoscaling
Mailing list
Open Community Issues/PRs
GitHub Teams:
- @kubernetes/sig-autoscaling-api-reviews - API Changes and Reviews
- @kubernetes/sig-autoscaling-bugs - Bug Triage and Troubleshooting
- @kubernetes/sig-autoscaling-feature-requests - Feature Requests
- @kubernetes/sig-autoscaling-misc - General Discussion
- @kubernetes/sig-autoscaling-pr-reviews - PR Reviews
- @kubernetes/sig-autoscaling-proposals - Design Proposals
- @kubernetes/sig-autoscaling-test-failures - Test Failures and Triage
Steering Committee Liaison: Maciej Szulik (@soltysh )

Working Groups

The following working groups are sponsored by sig-autoscaling:

Subprojects

The following subprojects are owned by sig-autoscaling:

addon-resizer

Owners:
- kubernetes/autoscaler/addon-resizer

cluster-autoscaler

Owners:
- kubernetes-sigs/cluster-autoscaler
- kubernetes/autoscaler/cluster-autoscaler

horizontal-pod-autoscaler

Owners:
- kubernetes/api/autoscaling
- kubernetes/kubernetes/pkg/controller/podautoscaler

karpenter

Owners:
Contact:
- Slack: #karpenter

vertical-pod-autoscaler

Owners:
- kubernetes/autoscaler/vertical-pod-autoscaler
Contact:
- Slack: #vertical-pod-autoscaler

Concerns

autoscaling of clusters,
horizontal and vertical autoscaling of pods,
setting initial resources for pods,
topics related to monitoring pods and gathering their metrics (e.g.: Heapster)

Demo and Presentation Guidelines

If you want to demo at SIG Autoscaling, we have some guidelines:

Demos should talk about open-source projects relevant to Kubernetes autoscaling, such as:
- Prototypes for features to be added to Kubernetes
- Projects that fill gaps in our infrastructure that we might want to address
- Alternative approaches to what we do now that we may want to research
Demos and presentations should be geared towards a techincal audience.
Demos and presentations should not talk about company history or background, except to provide context for a usecase or issue:
- “We’re a retail company, and people don’t shop as much during at 3am, so we generally see patterns of traffic around times” is acceptable.
- Giving a company elevator pitch is not acceptable.
Non-demo presentations should focus on usecases and issues. A good rule of thumb is that content should be relevant in some form to a design doc or KEP’s motivation or background sections. If it’s not, it probably doesn’t belong in the presentation.
Demos and presentations should not pitch products. If you want to talk about a product that’s recently been open-sourced, focus on it from the perspective of why it’s useful to the community.

Community: SIG CLI

Mon, 01 Jan 0001 00:00:00 +0000

CLI Special Interest Group

Covers kubectl and related tools. We focus on the development and standardization of the CLI framework and its dependencies, the establishment of conventions for writing CLI commands, POSIX compliance, and improving the command line tools from a developer and devops user experience and usability perspective.

The charter defines the scope and governance of the CLI Special Interest Group.

Meetings

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

Bug Scrub: Wednesdays at 09:00 PT (Pacific Time) (every four weeks). Convert to your timezone .
- Meeting notes and Agenda .
- Meeting recordings .
Regular SIG Meeting: Wednesdays at 09:00 PT (Pacific Time) (biweekly). Convert to your timezone .
- Meeting notes and Agenda .
- Meeting recordings .

Leadership

Chairs

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

Arda Guclu (@ardaguclu ), Red Hat
Marly Salazar (@mpuckett159 ), Independent

Technical Leads

The Technical Leads of the SIG establish new subprojects, decommission existing subprojects, and resolve cross-subproject technical issues and decisions.

Eddie Zaneski (@eddiezane ), Defense Unicorns
Maciej Szulik (@soltysh ), Defense Unicorns

Emeritus Leads

Tony Ado (@AdoHe )
Katrina Verey (@KnVerey )
Fabiano Franz (@fabianofranz )
Natasha Sarkar (@natasha41575 )
Phillip Wittrock (@pwittrock )
Sean Sullivan (@seans3 )

Contact

Slack: #sig-cli
Mailing list
Open Community Issues/PRs
GitHub Teams:
- @kubernetes/sig-cli-api-reviews - API Changes and Reviews
- @kubernetes/sig-cli-bugs - Bug Triage and Troubleshooting
- @kubernetes/sig-cli-feature-requests - Feature Requests
- @kubernetes/sig-cli-maintainers - CLI Maintainers
- @kubernetes/sig-cli-misc - General Discussion
- @kubernetes/sig-cli-pr-reviews - PR Reviews
- @kubernetes/sig-cli-proposals - Design Proposals
- @kubernetes/sig-cli-test-failures - Test Failures and Triage
Steering Committee Liaison: Paco Xu 徐俊杰 (@pacoxu )

Working Groups

The following working groups are sponsored by sig-cli:

WG Node Lifecycle

Subprojects

The following subprojects are owned by sig-cli:

cli-experimental

Owners:
- kubernetes-sigs/cli-experimental

cli-sdk

Owners:

cli-utils

Owners:
- kubernetes-sigs/cli-utils

krew

Plugin manager for kubectl.

Owners:
- kubernetes-sigs/krew

krew-index

Centralized plugin index for krew.

Owners:
- kubernetes-sigs/krew-index

kubectl

Owners:
- kubernetes/kubectl
- kubernetes/kubernetes/pkg/kubectl

kubectl-validate

CLI Tool for validating Kubernetes resources from their OpenAPIV3 schemas on client-side aiming for best parity with errors returned by server. Supports core resources, CRDs, CEL validations, and more!

Owners:
- kubernetes-sigs/kubectl-validate

kustomize

Leads:
- Yugo Kobayashi (@koba1t ), LY Corporation
Owners:
- kubernetes-sigs/kustomize
Contact:
- Slack: #kustomize

Community: SIG Cloud Provider

Mon, 01 Jan 0001 00:00:00 +0000

Cloud Provider Special Interest Group

Ensures that the Kubernetes ecosystem is evolving in a way that is neutral to all (public and private) cloud providers. It will be responsible for establishing standards and requirements that must be met by all providers to ensure optimal integration with Kubernetes.

The charter defines the scope and governance of the Cloud Provider Special Interest Group.

Meetings

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

Regular SIG Meeting: Wednesdays at 9:00 PT (Pacific Time) (biweekly). Convert to your timezone .
- Meeting notes and Agenda .
- Meeting recordings .

Leadership

Chairs

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

Bridget Kromhout (@bridgetkromhout ), Microsoft
Michael McCune (@elmiko ), Red Hat

Technical Leads

The Technical Leads of the SIG establish new subprojects, decommission existing subprojects, and resolve cross-subproject technical issues and decisions.

Walter Fender (@cheftako ), Google
Michael McCune (@elmiko ), Red Hat
Joel Speed (@joelspeed ), Red Hat

Emeritus Leads

Andrew Sy Kim (@andrewsykim )
Chris Hoge (@hogepodge )
Jago Macleod (@jagosan )
Nick Turner (@nckturner )

Contact

Slack: #sig-cloud-provider
Mailing list
Open Community Issues/PRs
GitHub Teams:
- @kubernetes/sig-cloud-provider-api-reviews - API Changes and Reviews
- @kubernetes/sig-cloud-provider-bugs - Bug Triage and Troubleshooting
- @kubernetes/sig-cloud-provider-feature-requests - Feature Requests
- @kubernetes/sig-cloud-provider-maintainers - Cloud Providers Maintainers
- @kubernetes/sig-cloud-provider-pr-reviews - PR Reviews
- @kubernetes/sig-cloud-provider-proposals - Design Proposals
- @kubernetes/sig-cloud-provider-test-failures - Test Failures and Triage
- @kubernetes/sig-cloud-providers-misc - General Discussion
Steering Committee Liaison: Maciej Szulik (@soltysh )

Working Groups

The following working groups are sponsored by sig-cloud-provider:

WG Node Lifecycle

Subprojects

The following subprojects are owned by sig-cloud-provider:

cloud-provider-extraction-migration

Owners:

kro

Simplify the creation and management of complex custom resources for Kubernetes.

Owners:
- kubernetes-sigs/kro/heads/main

kubernetes-cloud-provider

Owners:

provider-alibaba-cloud

Owners:
- kubernetes-sigs/alibaba-cloud-csi-driver
- kubernetes/cloud-provider-alibaba-cloud
Meetings:
- Regular Alibaba Cloud Subproject Meeting: Tuesdays at 12:00 UTC (monthly 2020 start date: Jan. 7th). Convert to your timezone .
  - Meeting notes and Agenda .
  - Meeting recordings .

provider-aws

Owners:
Meetings:
- Regular AWS Subproject Meeting: Fridays at 9:00 PT (Pacific Time) (biweekly 2019 start date: Jan. 11th). Convert to your timezone .
  - Meeting notes and Agenda .
  - Meeting recordings .

provider-azure

Owners:
Meetings:
- Azure Subproject Meeting: Tuesdays at 16:00 PT (Pacific Time) (monthly - third Tuesday). Convert to your timezone .
  - Meeting notes and Agenda .
  - Meeting recordings .

provider-equinix-metal

Owners:
- kubernetes-sigs/cloud-provider-equinix-metal

provider-gcp

Owners:
Meetings:
- Regular GCP Subproject Meeting: Thursdays at 16:00 UTC (biweekly). Convert to your timezone .
  - Meeting notes and Agenda .

provider-huaweicloud

Owners:
- kubernetes-sigs/cloud-provider-huaweicloud

provider-ibmcloud

Owners:
Meetings:
- Regular IBM Subproject Meeting: Wednesdays at 14:00 ET (Eastern Time) (monthly - last Wednesday every month). Convert to your timezone .
  - Meeting notes and Agenda .

provider-oci

Owners:
- oracle/cluster-api-provider-oci
Meetings:
- Regular Oracle Cloud Subproject Meeting: Tuesdays at 06:00 PT (Pacific Time) (First Tuesday of each month). Convert to your timezone .
  - Meeting notes and Agenda .

provider-openstack

Owners:
- kubernetes/cloud-provider-openstack
Meetings:
- Regular OpenStack Subproject Meeting: Wednesdays at 08:00 PT (Pacific Time) (biweekly starting Wednesday March 20, 2019). Convert to your timezone .
  - Meeting notes and Agenda .
  - Meeting recordings .

provider-vsphere

Owners:
- kubernetes-sigs/vsphere-csi-driver
- kubernetes/cloud-provider-vsphere
Meetings:
- Cloud Provider vSphere monthly syncup: Wednesdays at 09:00 PT (Pacific Time) (monthly - first Wednesday every month). Convert to your timezone .
  - Meeting notes and Agenda .
  - Meeting recordings .

Community: SIG Cluster Lifecycle

Mon, 01 Jan 0001 00:00:00 +0000

Cluster Lifecycle Special Interest Group

The Cluster Lifecycle SIG examines how we should change Kubernetes to make it easier to manage and operate with a focus on cluster deployment and upgrades. Add our calendar to track when we have community meetings.

The charter defines the scope and governance of the Cluster Lifecycle Special Interest Group.

Meetings

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

Regular SIG Meeting (calendar ) : Tuesdays at 09:00 PT (Pacific Time) (biweekly). Convert to your timezone .
- Meeting notes and Agenda .
- Meeting recordings .

Leadership

Chairs

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

Justin Santa Barbara (@justinsb ), Google
Lubomir Ivanov (@neolit123 ), Independent
Vince Prignano (@vincepri ), Red Hat

Technical Leads

The Technical Leads of the SIG establish new subprojects, decommission existing subprojects, and resolve cross-subproject technical issues and decisions.

Fabrizio Pandini (@fabriziopandini ), VMware

Emeritus Leads

Cecile Robert-Michon (@CecileRobertMichon )
Lucas Käldström (@luxas )
Robert Bailey (@roberthbailey )
Timothy St. Clair (@timothysc )

Contact

Slack: #sig-cluster-lifecycle
Mailing list
Open Community Issues/PRs
GitHub Teams:
- @kubernetes/sig-cluster-lifecycle - SIG Cluster Lifecycle mailing list
Steering Committee Liaison: Sascha Grunert (@saschagrunert )

Working Groups

The following working groups are sponsored by sig-cluster-lifecycle:

Subprojects

The following subprojects are owned by sig-cluster-lifecycle:

cluster-addons

A project for figuring out the best way to install, manage and deliver cluster addons

Owners:
- kubernetes-sigs/cluster-addons
Contact:
- Slack: #cluster-addons
- Mailing List
Meetings:
- Cluster Addons meeting: Tuesdays at 09:00 PT (Pacific Time) (biweekly). Convert to your timezone .
  - Meeting notes and Agenda .

cluster-api

A project focused on providing declarative APIs and tooling to simplify provisioning, upgrading, and operating multiple Kubernetes clusters

Owners:
- kubernetes-sigs/cluster-api
- kubernetes-sigs/logical-cluster
Contact:
- Slack: #cluster-api
- Mailing List
Meetings:
- Cluster API office hours: Wednesdays at 10:00 PT (Pacific Time) (weekly). Convert to your timezone .
  - Meeting notes and Agenda .
  - Meeting recordings .

cluster-api-addon-provider-helm

Implementation of Cluster Add-on Provider for Helm, an add-on orchestration solution for Cluster API using Helm.

Owners:
- kubernetes-sigs/cluster-api-addon-provider-helm
Contact:
- Slack: #cluster-api-addon-helm
- Mailing List

cluster-api-ipam-provider-in-cluster

Cluster API IPAM provider

Owners:
- kubernetes-sigs/cluster-api-ipam-provider-in-cluster

cluster-api-operator

Leverages a declarative API and an operator to empower admins to handle the lifecycle of Cluster API providers within the management cluster

Owners:
- kubernetes-sigs/cluster-api-operator
Contact:
- Slack: #cluster-api-operator
- Mailing List
Meetings:
- Cluster API Operator office hours: Wednesdays at 09:00 PT (Pacific Time) (every third Wednesday of the month). Convert to your timezone .
  - Meeting notes and Agenda .
  - Meeting recordings .

cluster-api-provider-aws

Cluster API infrastructure provider for AWS

Owners:
- kubernetes-sigs/cluster-api-provider-aws
Contact:
- Slack: #cluster-api-aws
- Mailing List
Meetings:
- Cluster API Provider AWS office hours: Mondays at 09:00 PT (Pacific Time) (biweekly). Convert to your timezone .
  - Meeting notes and Agenda .
  - Meeting recordings .

cluster-api-provider-azure

Cluster API infrastructure provider for Azure

Owners:
- kubernetes-sigs/cluster-api-provider-azure
Contact:
- Slack: #cluster-api-azure
- Mailing List
Meetings:
- Cluster API Provider Azure office hours: Thursdays at 09:00 PT (Pacific Time) (biweekly). Convert to your timezone .
  - Meeting notes and Agenda .
  - Meeting recordings .

cluster-api-provider-cloudstack

Cluster API provider for Apache Cloudstack

Owners:
- kubernetes-sigs/cluster-api-provider-cloudstack

cluster-api-provider-digitalocean

Cluster API infrastructure provider for DigitalOcean

Owners:
- kubernetes-sigs/cluster-api-provider-digitalocean
Contact:
- Slack: #cluster-api-digitalocean
- Mailing List
Meetings:
- Cluster API Provider DigitalOcean office hours: Thursdays at 09:00 PT (Pacific Time) (monthly, second Thursday of the month). Convert to your timezone .
  - Meeting notes and Agenda .
  - Meeting recordings .

cluster-api-provider-gcp

Cluster API infrastructure provider for GCP

Owners:
- kubernetes-sigs/cluster-api-provider-gcp
Contact:
- Slack: #cluster-api-gcp
- Mailing List
Meetings:
- Cluster API infrastructure provider for GCP: Thursdays at 05:00 PT (Pacific Time) (every first Thursday of the month). Convert to your timezone .
  - Meeting notes and Agenda .
  - Meeting recordings .

cluster-api-provider-ibmcloud

Cluster API infrastructure provider for IBM Cloud

Owners:
- kubernetes-sigs/cluster-api-provider-ibmcloud
Contact:
- Slack: #cluster-api-ibmcloud
- Mailing List
Meetings:
- Cluster API Provider IBM Cloud office hours: Thursdays at 14:00 IST (biweekly). Convert to your timezone .
  - Meeting notes and Agenda .
  - Meeting recordings .

cluster-api-provider-kubemark

Cluster API infrastructure provider for Kubemark

Owners:
- kubernetes-sigs/cluster-api-provider-kubemark
Contact:
- Slack: #cluster-api-kubemark
- Mailing List

cluster-api-provider-kubevirt

Cluster API infrastructure provider for KubeVirt

Owners:
- kubernetes-sigs/cluster-api-provider-kubevirt
Contact:
- Slack: #cluster-api-kubevirt
- Mailing List
Meetings:
- Cluster API Provider KubeVirt Syncup Meetings: Tuesdays at 8:00 PT (Pacific Time) (weekly starting Tuesday December 7th, 2021). Convert to your timezone .
  - Meeting notes and Agenda .

cluster-api-provider-openstack

Cluster API infrastructure provider for OpenStack

Owners:
- kubernetes-sigs/cluster-api-provider-openstack
Contact:
- Slack: #cluster-api-openstack
- Mailing List
Meetings:
- Cluster API Provider OpenStack Office Hours: Wednesdays at 12:00 UTC (biweekly). Convert to your timezone .
  - Meeting notes and Agenda .

cluster-api-provider-vsphere

Cluster API infrastructure provider for vSphere

Owners:
- kubernetes-sigs/cluster-api-provider-vsphere
Contact:
- Slack: #cluster-api-vsphere
- Mailing List
Meetings:
- Cluster API vSphere meeting: Thursdays at 10:00 PT (Pacific Time) (biweekly starting Thursday June 25th, 2020). Convert to your timezone .
  - Meeting notes and Agenda .
  - Meeting recordings .

image-builder

A collection of cross-provider Kubernetes virtual machine image building utilities

Owners:
- kubernetes-sigs/image-builder
Contact:
- Slack: #image-builder
- Mailing List
Meetings:
- Image Builder office hours: Mondays at 08:30 PT (Pacific Time) (biweekly). Convert to your timezone .
  - Meeting notes and Agenda .
  - Meeting recordings .

kOps

A tool for creating, destroying, upgrading and maintaining production-grade, highly available, Kubernetes cluster that also provisions infrastructure

Owners:
- kubernetes/kops
Contact:
- Slack: #kops-dev
- Mailing List
Meetings:
- kOps Office Hours: Fridays at 09:00 PT (Pacific Time) (biweekly). Convert to your timezone .
  - Meeting notes and Agenda .

karpenter-provider-cluster-api

Cluster API Karpenter provider

Owners:
- kubernetes-sigs/karpenter-provider-cluster-api/heads/main

kubeadm

A tool that performs the actions necessary to get a minimum viable, secure cluster up and running in a user friendly way

Owners:
Contact:
- Slack: #kubeadm
- Mailing List
Meetings:
- kubeadm Office Hours: Wednesdays at 09:00 PT (Pacific Time) (biweekly). Convert to your timezone .
  - Meeting notes and Agenda .
  - Meeting recordings .

kubespray

A project that uses Ansible / Vagrant for deploying production ready clusters on different infrastructure

Owners:
- kubernetes-sigs/kubespray
Contact:
- Slack: #kubespray
- Mailing List

minikube

Implements a local Kubernetes cluster for application development on macOS, Linux, and Windows

Owners:
Contact:
- Slack: #minikube
- Mailing List
Meetings:
- minikube office hours: Mondays at 11:00 PT (Pacific Time) (biweekly). Convert to your timezone .
  - Meeting notes and Agenda .

Community: SIG Contributor Experience

Mon, 01 Jan 0001 00:00:00 +0000

Contributor Experience Special Interest Group

Developing and sustaining a healthy community of contributors is critical to scaling the project and growing the ecosystem. We need to ensure our contributors are happy and productive, and that there are not bottlenecks hindering the project in, for example: feature velocity, community scaling, pull request latency, and absolute numbers of open pull requests and open issues.

The charter defines the scope and governance of the Contributor Experience Special Interest Group.

Meetings

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

Regular SIG Meeting: Wednesdays at 10:00 PT (Pacific Time) (Biweekly). Convert to your timezone .
- Meeting notes and Agenda .
- Meeting recordings .
Regular SIG Meeting (APAC/J/NZ timezone friendly): Wednesdays at 7:30 UTC (Biweekly, interleaved with the Regular SIG Meeting). Convert to your timezone .
- Meeting notes and Agenda .
- Meeting recordings .

Leadership

Chairs

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

Kaslin Fields (@kaslin ), Google
Mario Fahlandt (@mfahlandt ), Kubermatic GmbH
Nabarun Pal (@palnabarun ), Broadcom

Technical Leads

The Technical Leads of the SIG establish new subprojects, decommission existing subprojects, and resolve cross-subproject technical issues and decisions.

Madhav Jivrajani (@MadhavJivrajani ), VMware
Priyanka Saggu (@Priyankasaggu11929 ), SUSE

Emeritus Leads

Elsie Phillips (@Phillels )
Alison Dowdney (@alisondy )
Jorge Castro (@castrojo )
Christoph Blecker (@cblecker )
Garrett Rodrigues (@grodrigues3 )
Josh Berkus (@jberkus )
Bob Killen (@mrbobbytables )
Nikhita Raghunath (@nikhita )
Paris Pittman (@parispittman )

Contact

Slack: #sig-contribex
Mailing list
Open Community Issues/PRs
GitHub Teams:
- @kubernetes/sig-contributor-experience - General Discussion
- @kubernetes/sig-contributor-experience-leads - Chairs and Technical Leads
- @kubernetes/sig-contributor-experience-pr-reviews - PR Reviews
Steering Committee Liaison: Rita Zhang (@ritazh )

Subprojects

The following subprojects are owned by sig-contributor-experience:

community

Owns and manages overall community repo, including community group documentation and operations.

Owners:
- kubernetes/community

community-management

Manages operations and policy for upstream community group communication platforms.

Owners:
- kubernetes-sigs/discuss-theme
- kubernetes/community/communication

contributor-comms

Contributor Communications focuses on amplifying the success of Kubernetes contributors through marketing.

Owners:
- kubernetes-sigs/lwkd
- kubernetes/community/communication/contributor-comms
Meetings:
- Contributor Comms - Contributor Comms Team Meeting: Fridays at 8:00 PT (Pacific Time) (weekly). Convert to your timezone .
  - Meeting notes and Agenda .
  - Meeting recordings .

contributors-documentation

writes and maintains documentation around contributing to Kubernetes, including the Contributor’s Guide, Developer’s Guide, and contributor website.

Owners:
- kubernetes/community/contributors/guide
- kubernetes/contributor-site

devstats

Maintains and updates https://k8s.devstats.cncf.io , including taking requests for new charts.

Owners:
- kubernetes/community/sig-contributor-experience/devstats
Contact:
- Slack: #devstats

elections

Oversees running elections in the community. Maintains documentation and software for elections.

Owners:
- kubernetes/community/elections
Contact:
- Slack: #sig-contribex

events

Creates and runs contributor-focused events, such as the Contributor Summit. Event Teams are part of this subproject.

Owners:
- kubernetes/community/events
Contact:
- Slack: #sig-contribex

github-management

Manages and controls Github permissions, repos, and groups, including Org Membership.

Owners:
Contact:
- Slack: #github-management
Meetings:
- GitHub Administration Subproject: Thursdays at 09:00 PT (Pacific Time) (Monthly on 4th Thursday). Convert to your timezone .
  - Meeting notes and Agenda .
  - Meeting recordings .

mentoring

Oversees and develops programs for helping contributors ascend the contributor ladder, including the New Contributor Workshops, and other programs.

Owners:
- kubernetes-sigs/contributor-playground
- kubernetes/community/mentoring

slack-infra

Creates and maintains tools and automation for Kubernetes Slack.

Owners:
- kubernetes-sigs/slack-infra
Contact:
- Slack: #slack-infra

Relevant Presentations

This is a collection of presentations from our SIG members around contributing to Kubernetes, feel free to PR in content here:

Current Status

This is the work we’ve done this past cycle and plan to work on in the future:

From Automation to Community: A Deep Dive Into SIG Contributor Experience (April 2023)
- Slides

General Presentations

How to Contribute to Kubernetes - Nikhita Raghunath
Practical git for Kubernetes Contributors - Christoph Blecker
State of the Kubernetes Contributor Community - Paris Pittman
A peek behind the curtain: Managing the Kubernetes Contributor Community

KubeCon + CloudNativeCon

We give our SIG status at every KubeCon, here are our most current talks:

From Automation to Community: A Deep Dive Into SIG Contributor Experience, Europe 2023 - Madhav Jivrajani, Priyanka Saggu, Kaslin Fields
SIG Contributor Experience Deep Dive, North America 2022 - Nabarun Pal & Madhav Jivrajani, Marky Jackson, Kaslin Fields
SIG Contributor Experience Deep Dive, Europe 2022 - Alison Dowdney, Christoph Blecker, Bob Killen
SIG Contributor Experience Deep Dive, North America 2021 - Alison Dowdney, Christoph Blecker
SIG Contributor Experience Deep Dive, Europe 2021 - Bob Killen, Alison Dowdney, Christoph Blecker, Nikhita Raghunath
Introdution to Contributor Experience 2020 - Bob Killen, Jorge Castro
Introduction to Contributor Experience 2019 - Elsie Phillips, Paris Pittman
Contributor Experience Deep Dive 2019 - Christoph Blecker, Nikhita Raghunath

Community: SIG Docs

Mon, 01 Jan 0001 00:00:00 +0000

Docs Special Interest Group

Covers documentation, doc processes, and doc publishing for Kubernetes.

The charter defines the scope and governance of the Docs Special Interest Group.

Meetings

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

APAC SIG Meeting: Wednesdays at 05:30 UTC (monthly - Wednesday, after the fourth Tuesday, every month). Convert to your timezone .
- Meeting notes and Agenda .
- Meeting recordings .
Korean Team Meeting: Thursdays at 13:00 UTC (biweekly). Convert to your timezone .
- Meeting notes and Agenda .
- Meeting recordings .
Localization Subproject Meeting: Mondays at 15:00 UTC (first Monday of the month). Convert to your timezone .
- Meeting notes and Agenda .
- Meeting recordings .
New Contributor Meet and Greet: Tuesdays at 10:30 UTC (first Tuesday of the month). Convert to your timezone .
- Meeting notes and Agenda .
- Meeting recordings .
Regular SIG Meeting: Tuesdays at 17:30 UTC (biweekly). Convert to your timezone .
- Meeting notes and Agenda .
- Meeting recordings .
Spanish Team Meeting: Tuesdays at 15:30 UTC (weekly). Convert to your timezone .
- Meeting notes and Agenda .
- Meeting recordings .

Leadership

Chairs

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

Divya Mohan (@divya-mohan0209 ), SUSE
Natali Vlatko (@natalisucks ), Cisco
Rey Lejano (@reylejano ), Red Hat

Technical Leads

The Technical Leads of the SIG establish new subprojects, decommission existing subprojects, and resolve cross-subproject technical issues and decisions.

Dipesh Rawat (@dipesh-rawat ), IBM
Kat Cosgrove (@katcosgrove ), Minimus
Rey Lejano (@reylejano ), Red Hat
Xander Grzywinski (@salaxander ), Independent
Qiming Teng (@tengqm ), Sangfor Technologies

Emeritus Leads

Jennifer Rondeau (@Bradamant3 )
Andrew Chen (@chenopis )
Irvi Aini (@irvifa )
Jared Bhatti (@jaredbhatti )
Jim Angel (@jimangel )
Kaitlyn Barnard (@kbarnard10 )
Karen Bradshaw (@kbhawkey )
Taylor Dolezal (@onlydole )
Tim Bannister (@sftim )
Sarah Corleissen (@zacharysarah )

Contact

Slack: #sig-docs
Mailing list
Open Community Issues/PRs
GitHub Teams:
- @kubernetes/sig-docs-blog-owners - Kubernetes blog maintainers
- @kubernetes/sig-docs-de-owners - German language content
- @kubernetes/sig-docs-en-owners - English content (default)
- @kubernetes/sig-docs-es-owners - Spanish language content
- @kubernetes/sig-docs-fr-owners - French language content
- @kubernetes/sig-docs-hi-owners - Hindi language content
- @kubernetes/sig-docs-id-owners - Indonesian language content
- @kubernetes/sig-docs-it-owners - Italian language content
- @kubernetes/sig-docs-ja-owners - Japanese language content
- @kubernetes/sig-docs-ko-owners - Korean language content
- @kubernetes/sig-docs-maintainers - Documentation maintainers
- @kubernetes/sig-docs-pl-owners - Polish language content
- @kubernetes/sig-docs-pr-reviews - Documentation PR reviews
- @kubernetes/sig-docs-pt-owners - Portuguese language content
- @kubernetes/sig-docs-ru-owners - Russian language content
- @kubernetes/sig-docs-uk-owners - Ukrainian language content
- @kubernetes/sig-docs-zh-owners - Chinese language content
Steering Committee Liaison: Kat Cosgrove (@katcosgrove )

Subprojects

The following subprojects are owned by sig-docs:

kubernetes-blog

Owners:
- kubernetes/website/content/en/blog

localization

Owners:
- kubernetes/website

reference-docs

Owners:
- kubernetes-sigs/reference-docs

website

Owners:
- kubernetes/website

Community: SIG etcd

Mon, 01 Jan 0001 00:00:00 +0000

etcd Special Interest Group

etcd is a production-ready store for building cloud-native distributed systems and managing cloud-native infrastructure via orchestrators like Kubernetes. Etcd should provide distributed system primitives** (such as distributed locking and leader election) that allow users to **create scalable, highly available and fault-tolerant systems. Etcd is the place to store the infrastructure configuration, not only as part of Kubernetes, but also as a standalone solution.

The charter defines the scope and governance of the etcd Special Interest Group.

Meetings

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

Docs Meeting: Tuesdays at 17: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 .
Robustness Tests Meeting: Wednesdays at 11:00 PT (Pacific Time) (biweekly). Convert to your timezone .
- Meeting notes and Agenda .
- Meeting recordings .
Triage Meeting: Thursdays at 11:00 PT (Pacific Time) (biweekly). Convert to your timezone .
- Meeting notes and Agenda .
- Meeting recordings .

Leadership

Chairs

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

Ivan Valdes (@ivanvc ), Inmar Intelligence
Josh Berkus (@jberkus ), Red Hat
Siyuan Zhang (@siyuanfoundation ), Google

Technical Leads

The Technical Leads of the SIG establish new subprojects, decommission existing subprojects, and resolve cross-subproject technical issues and decisions.

Benjamin Wang (@ahrtr ), VMware
Marek Siarkowicz (@serathius ), Google

Emeritus Leads

James Blair (@jmhbnz )
Wenjia Zhang (@wenjiaswe )

Contact

Slack: #sig-etcd
Mailing list
Open Community Issues/PRs
GitHub Teams:
- @kubernetes/sig-etcd-leads - SIG Chairs and Tech Leads
Steering Committee Liaison: Antonio Ojea (@aojea )

Working Groups

The following working groups are sponsored by sig-etcd:

WG etcd Operator

Subprojects

The following subprojects are owned by sig-etcd:

auger

Directly access data objects stored in etcd by kubernetes.

Owners:
- etcd-io/auger

bbolt

An embedded key/value database for Go.

Owners:
- etcd-io/bbolt

cetcd

Serve Consul with etcd

Owners:
- etcd-io/cetcd/MAINTAINERS

dbtester

Distributed database benchmark tester

Owners:
- etcd-io/dbtester/MAINTAINERS

discovery.etcd.io

Kubernetes manifests powering discovery.etcd.io

Owners:
- etcd-io/discovery.etcd.io

discoveryserver

Public etcd Discovery Service

Owners:
- etcd-io/discoveryserver

etcd

Distributed reliable key-value store for the most critical data of a distributed system

Owners:
- etcd-io/etcd

etcd-manager

etcd manager

Owners:
- kubernetes-sigs/etcd-manager

etcd-operator

future site of the new etcd operator, currently used for wg-etcd-operator artifacts

Owners:
- etcd-io/etcd-operator

etcd-play

etcd playground

Owners:
- etcd-io/etcd-play/MAINTAINERS

etcdlabs

etcd playground

Owners:
- etcd-io/etcdlabs/MAINTAINERS

gofail

failpoints for go

Owners:
- etcd-io/gofail

govanityurls

Use a custom domain in your Go import path

Owners:
- etcd-io/govanityurls

jetcd

etcd java client

Owners:
- etcd-io/jetcd

maintainers

issue tracking for project wide non-code concerns

Owners:
- etcd-io/maintainers/MAINTAINERS

protodoc

protodoc generates Protocol Buffer documentation.

Owners:
- etcd-io/protodoc

raft

Raft library for maintaining a replicated state machine

Owners:
- etcd-io/raft

website

etcd-io

Owners:
- etcd-io/website

zetcd

Serve the Apache Zookeeper API but back it with an etcd cluster

Owners:
- etcd-io/zetcd/MAINTAINERS

Community: SIG Instrumentation

Mon, 01 Jan 0001 00:00:00 +0000

Instrumentation Special Interest Group

Covers best practices for cluster observability through metrics, logging, events, and traces across all Kubernetes components and development of relevant components such as klog and kube-state-metrics. Coordinates metric requirements of different SIGs for other components through finding common APIs.

The charter defines the scope and governance of the Instrumentation Special Interest Group.

Meetings

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

Regular SIG Meeting: Fridays at 8:30 PT (Pacific Time) (biweekly). Convert to your timezone .
- Meeting notes and Agenda .
- Meeting recordings .
Regular Triage Meeting: Fridays at 8:30 PT (Pacific Time) (biweekly - alternating with regular meeting). Convert to your timezone .
- Meeting notes and Agenda .

Leadership

Chairs

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

Pranshu Srivastava (@rexagod ), Red Hat
Richa Banker (@richabanker ), Google

Technical Leads

The Technical Leads of the SIG establish new subprojects, decommission existing subprojects, and resolve cross-subproject technical issues and decisions.

David Ashpole (@dashpole ), Google
Damien Grisonnet (@dgrisonnet ), Red Hat
Patrick Ohly (@pohly ), Intel

Emeritus Leads

Frederic Branczyk (@brancz )
Elana Hashman (@ehashman )
Han Kang (@logicalhan )
Piotr Szczesniak (@piosz )

Contact

Slack: #sig-instrumentation
Mailing list
Open Community Issues/PRs
GitHub Teams:
- @kubernetes/sig-instrumentation-approvers - SIG Top-level Approvers
- @kubernetes/sig-instrumentation-leads - SIG Chairs and Tech Leads
- @kubernetes/sig-instrumentation-members - SIG Membership Roster
Steering Committee Liaison: Rita Zhang (@ritazh )

Subprojects

The following subprojects are owned by sig-instrumentation:

custom-metrics-apiserver

Owners:
- kubernetes-sigs/custom-metrics-apiserver

instrumentation

Organization of SIG Instrumentation subprojects

Owners:
- kubernetes-sigs/instrumentation

instrumentation-addons

Owners:
- kubernetes-sigs/instrumentation-addons

instrumentation-tools

Owners:
- kubernetes-sigs/instrumentation-tools

klog

Owners:
- kubernetes/klog
Contact:
- Slack: #klog

kube-state-metrics

Owners:
- kubernetes/kube-state-metrics
Contact:
- Slack: #kube-state-metrics

metric-stability-framework

Owners:
- kubernetes/kubernetes/staging/src/k8s.io/component-base/metrics

metrics

Owners:
- kubernetes/kubernetes/staging/src/k8s.io/metrics
- kubernetes/metrics

metrics-server

Owners:
- kubernetes-sigs/metrics-server

prometheus-adapter

Owners:
- kubernetes-sigs/prometheus-adapter

resource-state-metrics

Owners:
- kubernetes-sigs/resource-state-metrics

usage-metrics-collector

Owners:
- kubernetes-sigs/usage-metrics-collector

Community: SIG K8s Infra

Mon, 01 Jan 0001 00:00:00 +0000

K8s Infra Special Interest Group

SIG K8s Infra is interested in the successful migration of ownership and management of all Kubernetes project infrastructure from the google.com GCP Organization (or elsewhere) to the CNCF, such that the Kubernetes project is able to sustainably operate itself without direct assistance from external vendors or entities. In other words, we seek to eradicate usage of the phrase “oh that’s something that only an employee of Vendor X can do, we’re blocked until they respond.”

The charter defines the scope and governance of the K8s Infra Special Interest Group.

Meetings

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

Regular SIG Meeting: Wednesdays at 17:00 UTC (bi-weekly). Convert to your timezone .
- Meeting notes and Agenda .
- Meeting recordings .

Leadership

Chairs

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

Dylan-Daniel Page (@GenPage ), Lambda AI
Arnaud Meukam (@ameukam ), Independent
Ciprian Hacman (@hakman ), Microsoft

Technical Leads

The Technical Leads of the SIG establish new subprojects, decommission existing subprojects, and resolve cross-subproject technical issues and decisions.

Arnaud Meukam (@ameukam ), Independent
Mahamed Ali (@upodroid ), Cisco
Marko Mudrinić (@xmudrii ), Kubermatic

Emeritus Leads

Benjamin Elder (@BenTheElder )
Bart Smykla (@bartsmykla )
Davanum Srinivas (@dims )
Aaron Crickenberger (@spiffxp )
Tim Hockin (@thockin )

Contact

Slack: #sig-k8s-infra
Mailing list
Open Community Issues/PRs
GitHub Teams:
- @kubernetes/sig-k8s-infra - active contributors in sig-k8s-infra
- @kubernetes/sig-k8s-infra-leads - sig-k8s-infra chairs and tech leads
Steering Committee Liaison: Rita Zhang (@ritazh )

Subprojects

The following subprojects are owned by sig-k8s-infra:

community-images

kubectl plugin used to highlight images pulled from community-owned registries

Owners:
- kubernetes-sigs/community-images
Contact:
- Slack: #sig-k8s-infra
- Mailing List

k8s-infra-dns

Code and configuration to manage DNS records for domains owned by the Kubernetes project such as k8s.io and kubernetes.io

Owners:
- kubernetes/k8s.io/dns
Contact:
- Slack: #sig-k8s-infra
- Mailing List
Meetings:
- Regular SIG Meeting: Wednesdays at 17:00 UTC (bi-weekly). Convert to your timezone .
  - Meeting notes and Agenda .
  - Meeting recordings .

k8s-infra-groups

Code and configuration to manage Google Groups for domains owned by the Kubernetes project such kubernetes.io

Owners:
- kubernetes/k8s.io/groups
Contact:
- Slack: #sig-k8s-infra
- Mailing List
Meetings:
- Regular SIG Meeting: Wednesdays at 17:00 UTC (bi-weekly). Convert to your timezone .
  - Meeting notes and Agenda .
  - Meeting recordings .

k8s.io

Code and configuration to manage Kubernetes project infrastructure, including various *.k8s.io sites

Owners:
- kubernetes/k8s.io
Contact:
- Slack: #sig-k8s-infra
- Mailing List
Meetings:
- Regular SIG Meeting: Wednesdays at 17:00 UTC (bi-weekly). Convert to your timezone .
  - Meeting notes and Agenda .
  - Meeting recordings .

porche

A custom HTTP redirector serving Kubernetes binaries from existing vendor supported and approved storage services.

Owners:
- kubernetes-sigs/porche
Contact:
- Slack: #sig-k8s-infra
- Mailing List
Meetings:
- Regular SIG Meeting: Wednesdays at 17:00 UTC (bi-weekly). Convert to your timezone .
  - Meeting notes and Agenda .
  - Meeting recordings .

registry.k8s.io

A custom HTTP redirector serving Kubernetes container image blobs from existing vendor supported container registries.

Owners:
- kubernetes/registry.k8s.io
Contact:
- Slack: #sig-k8s-infra
- Mailing List
Meetings:
- Regular SIG Meeting: Wednesdays at 17:00 UTC (bi-weekly). Convert to your timezone .
  - Meeting notes and Agenda .
  - Meeting recordings .

Community: SIG Multicluster

Mon, 01 Jan 0001 00:00:00 +0000

Multicluster Special Interest Group

A Special Interest Group focused on solving common challenges related to the management of multiple Kubernetes clusters, and applications that exist therein. The SIG will be responsible for designing, discussing, implementing and maintaining API’s, tools and documentation related to multi-cluster administration and application management. This includes not only active automated approaches such as Cluster Federation, but also those that employ batch workflow-style continuous deployment systems like Spinnaker and others. Standalone building blocks for these and other similar systems (for example a cluster registry), and proposed changes to kubernetes core where appropriate will also be in scope.

The charter defines the scope and governance of the Multicluster Special Interest Group.

Meetings

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

APAC-Friendly SIG Meeting: Thursdays at 6:30 UTC (bi-weekly). Convert to your timezone .
- Meeting notes and Agenda .
- Meeting recordings .
Regular SIG Meeting: Tuesdays at 9:30 PT (Pacific Time) (weekly). Convert to your timezone .
- Meeting notes and Agenda .
- Meeting recordings .

Leadership

Chairs

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

Jeremy Olmsted-Thompson (@jeremyot ), Google
Stephen Kitt (@skitt ), Red Hat

Emeritus Leads

Paul Morie (@pmorie )
Quinton Hoole (@quinton-hoole )

Contact

Slack: #sig-multicluster
Mailing list
Open Community Issues/PRs
GitHub Teams:
- @kubernetes/sig-multicluster-api-reviews - API Changes and Reviews
- @kubernetes/sig-multicluster-bugs - Bug Triage and Troubleshooting
- @kubernetes/sig-multicluster-feature-requests - Feature Requests
- @kubernetes/sig-multicluster-misc - General Discussion
- @kubernetes/sig-multicluster-pr-reviews - PR Reviews
- @kubernetes/sig-multicluster-proposals - Design Proposals
- @kubernetes/sig-multicluster-test-failures - Test Failures and Triage
Steering Committee Liaison: Antonio Ojea (@aojea )

Working Groups

The following working groups are sponsored by sig-multicluster:

WG AI Gateway

Subprojects

The following subprojects are owned by sig-multicluster:

about-api

Owners:
- kubernetes-sigs/about-api

cluster-inventory-api

Owners:
- kubernetes-sigs/cluster-inventory-api

mcs-api

Owners:
- kubernetes-sigs/mcs-api

multicluster-runtime

Owners:
- kubernetes-sigs/multicluster-runtime

sig-multicluster-site

Owners:
- kubernetes-sigs/sig-multicluster-site

work-api

Owners:
- kubernetes-sigs/work-api

Community: SIG Network

Mon, 01 Jan 0001 00:00:00 +0000

Network Special Interest Group

Covers networking in Kubernetes.

The charter defines the scope and governance of the Network Special Interest Group.

Meetings

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

Gateway API Meeting (Americas): Mondays at 15:00 PT (Pacific Time) (weekly). Convert to your timezone .
- Meeting notes and Agenda .
Gateway API Meeting (Europe): Tuesday (starting September 10th 2024)s at 08:00 PT (Pacific Time) (bi-weekly). Convert to your timezone .
- Meeting notes and Agenda .
Network Policy API Meeting: Tuesdays at 9:00 PT (Pacific Time) (bi-weekly). Convert to your timezone .
- Meeting notes and Agenda .
SIG Network Ingress NGINX Meeting: Thursdays at 8:00 PT (Pacific Time) (monthly). Convert to your timezone .
- Meeting notes and Agenda .
- Meeting recordings .
SIG Network Meeting: Thursdays at 09:00 PT (Pacific Time) (biweekly). Convert to your timezone .
- Meeting notes and Agenda .
- Meeting recordings .
SIG Network Multi-Network Meeting: Tuesdays at 06:00 PT (Pacific Time) (biweekly starting Tuesday Oct 28, 2025). Convert to your timezone .
- Meeting notes and Agenda .
- Meeting recordings .

Leadership

Chairs

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

Bowei Du (@bowei ), Google
Guilherme Cassolato (@guicassolato ), Red Hat
Michael Zappa (@mikezappa87 ), Microsoft

Technical Leads

The Technical Leads of the SIG establish new subprojects, decommission existing subprojects, and resolve cross-subproject technical issues and decisions.

Antonio Ojea (@aojea ), Google
Dan Winship (@danwinship ), Red Hat
Tim Hockin (@thockin ), Google

Emeritus Leads

Casey Davenport (@caseydavenport )
Dan Williams (@dcbw )
Shane Utt (@shaneutt )

Contact

Slack: #sig-network
Mailing list
Open Community Issues/PRs
GitHub Teams:
- @kubernetes/sig-network-api-reviews - API Changes and Reviews
- @kubernetes/sig-network-bugs - Bug Triage and Troubleshooting
- @kubernetes/sig-network-feature-requests - Feature Requests
- @kubernetes/sig-network-misc - General Discussion
- @kubernetes/sig-network-pr-reviews - PR Reviews
- @kubernetes/sig-network-proposals - Design Proposals
- @kubernetes/sig-network-test-failures - Test Failures and Triage
Steering Committee Liaison: Maciej Szulik (@soltysh )

Working Groups

The following working groups are sponsored by sig-network:

Subprojects

The following subprojects are owned by sig-network:

cluster-proportional-autoscaler

Owners:
- kubernetes-sigs/cluster-proportional-autoscaler

cluster-proportional-vertical-autoscaler

Owners:
- kubernetes-sigs/cluster-proportional-vertical-autoscaler

external-dns

Owners:
- kubernetes-sigs/external-dns
Contact:
- Slack: #external-dns

gateway-api

Leads:
- Ricardo Katz (@rikatz ), Red Hat
- Rob Scott (@robscott ), Google
- Nick Young (@youngnick ), Isovalent
Owners:
Contact:
- Slack: #sig-network-gateway-api

gateway-api-inference-extension

Gateway API Inference Extension

Owners:
- kubernetes-sigs/gateway-api-inference-extension
Contact:
- Slack: #gateway-api-inference-extension

ingate

Owners:
- kubernetes-sigs/ingate/heads/main

ingress

Owners:

iptables-wrappers

Owners:
- kubernetes-sigs/iptables-wrappers

kindnet

Owners:
- kubernetes-sigs/kindnet

knftables

Owners:
- kubernetes-sigs/knftables

kube-agentic-networking

Owners:
- kubernetes-sigs/kube-agentic-networking

kube-dns

kube-dns was the original implementation of Kubernetes Service DNS. It is now deprecated, though there may be new releases to fix CVEs up until Kubernetes 1.40. Most Kubernetes clusters now use CoreDNS for Service DNS.

Owners:
- kubernetes-sigs/node-local-dns
- kubernetes/dns

kubernetes-network-drivers

Owners:
- kubernetes-sigs/dranet
- kubernetes-sigs/kubernetes-network-drivers
Contact:
- Slack: #sig-network-dranet

multi-network

Leads:
- Lionel Jouin (@LionelJouin ), Red Hat
- Maciej Skrocki (@mskrocki ), Google
Owners:
- kubernetes-sigs/multi-network-api
- kubernetes-sigs/multi-network
Contact:
- Slack: #sig-network-multi-network

network-policy

Leads:
- Dan Winship (@danwinship ), Red Hat
- Nadia Pinaeva (@npinaeva ), NVIDIA
- Surya Seetharaman (@tssurya ), Red Hat
Owners:
Contact:
- Slack: #sig-network-policy-api

node-ipam-controller

Owners:
- kubernetes-sigs/node-ipam-controller

node-local-dns

Owners:
- kubernetes-sigs/node-local-dns

pod-networking

Owners:

wg-ai-gateway

Proposals and discussions for the AI Gateway Working Group

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

Subproject Leads

SIG network provides some additional responsibilities for subproject leads beyond what is covered in the standard subproject definition . Most of these additional responsibilities relate to communication about their projects within SIG Network, and to the greater community:

Transparent Project Planning, Maintenance and Communication:
- Subproject Leads must provide transparent view into their historical and future project plans (eg; using GitHub project boards, KEPs, or custom enhancement proposals (see GEPs /NPEPs )).
- Subproject leads must create, maintain and be present in a public Kubernetes Slack channel with the easy-to-find naming #sig-network-<subproject> for their sub-project.
- Subproject leads should create and maintain a regular public Zoom sync on the SIG Network Calendar .
- Subproject leads must keep the project in good health through regular issue triaging, PR reviews, CI health monitoring and checking testgrids (delegating this to other members in the community is good!)
- Projects that own CRDs in the k8s.io group must go through the API review process and Subproject leads are expected to make sure this well defined processes across Kubernetes is followed.
Regular Project Updates
- Subproject leads must report on project’s status, significant releases/events, interesting developments to the wider SIG-Network community via the SIG Network Mailing List on a quarterly basis (or as needed).
- Subproject leads should report on project status in the general SIG Network community meetings (in addition to mailing list updates).

Areas of Responsibility

SIG Network is responsible for the following Kubernetes subsystems:

DNS
Ingress
Network plugins / CNI
Network Policy
Services / kube-proxy

SIG Network is responsible for a number of issues and PRs. A summary can be found through GitHub search:

Documents

2017 Planning

Community: SIG Node

Mon, 01 Jan 0001 00:00:00 +0000

Node Special Interest Group

SIG Node is responsible for the components that support the controlled interactions between pods and host resources.

The charter defines the scope and governance of the Node Special Interest Group.

Meetings

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

Main SIG Meeting: Tuesdays at 10:00 PT (Pacific Time) (weekly). Convert to your timezone .
- Meeting notes and Agenda .
- Meeting recordings .
Weekly CI/Triage Meeting: Wednesdays at 10:00 PT (Pacific Time) (weekly). Convert to your timezone .
- Meeting notes and Agenda .
- Meeting recordings .

Leadership

Chairs

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

Sergey Kanzhelev (@SergeyKanzhelev ), Google
Peter Hunt (@haircommander ), Red Hat
Mrunal Patel (@mrunalp ), Red Hat

Technical Leads

The Technical Leads of the SIG establish new subprojects, decommission existing subprojects, and resolve cross-subproject technical issues and decisions.

Dawn Chen (@dchen1107 ), Google
Derek Carr (@derekwaynecarr ), Red Hat
Mrunal Patel (@mrunalp ), Red Hat

Contact

Slack: #sig-node
Mailing list
Open Community Issues/PRs
GitHub Teams:
- @kubernetes/sig-node-api-reviews - API Changes and Reviews
- @kubernetes/sig-node-bugs - Bug Triage and Troubleshooting
- @kubernetes/sig-node-feature-requests - Feature Requests
- @kubernetes/sig-node-pr-reviews - PR Reviews
- @kubernetes/sig-node-proposals - Design Proposals
- @kubernetes/sig-node-test-failures - Test Failures and Triage
Steering Committee Liaison: Paco Xu 徐俊杰 (@pacoxu )

Working Groups

The following working groups are sponsored by sig-node:

Subprojects

The following subprojects are owned by sig-node:

ci-testing

cri-api

Owners:

cri-client

Owners:
- kubernetes/cri-client
- kubernetes/kubernetes/staging/src/k8s.io/cri-client

cri-streaming

Owners:
- kubernetes/cri-streaming
- kubernetes/kubernetes/staging/src/k8s.io/cri-streaming

cri-tools

Owners:
- kubernetes-sigs/cri-tools

dra-driver-google-tpu

Owners:
- kubernetes-sigs/dra-driver-google-tpu

dra-driver-nvidia-gpu

Owners:
- kubernetes-sigs/dra-driver-nvidia-gpu

kernel-module-management

Owners:
- kubernetes-sigs/kernel-module-management

kubelet

Owners:

node-api

Owners:
- kubernetes/api/node
- kubernetes/kubernetes/staging/src/k8s.io/api/node

node-feature-discovery

Owners:
- kubernetes-sigs/node-feature-discovery-operator
- kubernetes-sigs/node-feature-discovery

node-problem-detector

Owners:
- kubernetes/node-problem-detector
- kubernetes/test-infra/config/jobs/kubernetes/node-problem-detector
Contact:
- Slack: #node-problem-detector

node-readiness-controller

Owners:
- kubernetes-sigs/node-readiness-controller

resource-management

Owners:

security-profiles-operator

Owners:
- kubernetes-sigs/security-profiles-operator
Contact:
- Slack: #security-profiles-operator

streaming

Owners:
- kubernetes/kubernetes/staging/src/k8s.io/streaming
- kubernetes/streaming

Goals

The following topics fall under scope of this SIG.

Kubelet and its features
Pod API and Pod behaviors (with sig-architecture )
Node API (with sig-architecture )
Node controller
Node level performance and scalability (with sig-scalability )
Node reliability (problem detection and remediation)
Node lifecycle management (with sig-cluster-lifecycle )
Container runtimes
Device management
Image management
Node-level resource management (with sig-scheduling )
Hardware discovery
Issues related to node, pod, container monitoring (with sig-instrumentation )
Node level security and Pod isolation (with sig-auth )
Host OS and/or kernel interactions (to a limited extent)

We also work closely with sig-storage and sig-network . As you can see, this is a very cross-functional team!

Subgroups

Read the CI testing subgroup charter .

Community: SIG Release

Mon, 01 Jan 0001 00:00:00 +0000

Release Special Interest Group

Ensure quality Kubernetes releases

The charter defines the scope and governance of the Release Special Interest Group.

Meetings

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

Regular SIG Meeting: Thursdays at 14:30 UTC (biweekly). Convert to your timezone .
- Meeting notes and Agenda .
- Meeting recordings .

Leadership

Chairs

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

Jeremy Rickard (@jeremyrickard ), Microsoft
Stephen Augustus (@justaugustus ), Bloomberg
Sascha Grunert (@saschagrunert ), Red Hat

Technical Leads

The Technical Leads of the SIG establish new subprojects, decommission existing subprojects, and resolve cross-subproject technical issues and decisions.

Verónica López (@Verolop ), AuthZed
Carlos Tadeu Panato Jr. (@cpanato ), Chainguard, Inc
Adolfo García Veytia (@puerco ), Carabiner Systems, Inc

Emeritus Leads

Jorge Alarcon Ochoa (@alejandrox1 )
Caleb Miles (@calebamiles )
Daniel Mangum (@hasheddan )
Jaice Singer DuMars (@jdumars )
Tim Pepper (@tpepper )

Contact

Slack: #sig-release
Mailing list
Open Community Issues/PRs
GitHub Teams:
- @kubernetes/milestone-maintainers - Milestone Maintainers
- @kubernetes/sig-release - SIG Release Members
- @kubernetes/sig-release-admins - Admins for SIG Release repositories
- @kubernetes/sig-release-leads - Chairs, Technical Leads, and Program Managers for SIG Release
Steering Committee Liaison: Rita Zhang (@ritazh )

Subprojects

The following subprojects are owned by sig-release:

Release Engineering

The Release Engineering subproject is responsible for the process/procedures and tools used to create/maintain Kubernetes release artifacts.

Leads:
- Marko Mudrinić (@xmudrii ), Kubermatic
Owners:
Contact:

Release Team

The Kubernetes Release Team is responsible for the day-to-day work required to successfully create releases of Kubernetes.

Leads:
- Frederico Munoz (@fsmunoz ), SAS
- Kat Cosgrove (@katcosgrove ), Minimus
Owners:
Contact:
- Mailing List
- GitHub Teams:
  - @kubernetes/release-ci-signal
  - @kubernetes/release-team - Members of the current Release Team and subproject owners
  - @kubernetes/release-team-bug-triage
  - @kubernetes/release-team-comms
  - @kubernetes/release-team-docs
  - @kubernetes/release-team-enhancements
  - @kubernetes/release-team-leads - Release Team Leads for the current Kubernetes release cycle
  - @kubernetes/release-team-release-notes

SIG Release Process Documentation

Documents and processes related to SIG Release

Owners:
- kubernetes/sig-release

The canonical location for SIG Release information is kubernetes/sig-release .

Community: SIG Scalability

Mon, 01 Jan 0001 00:00:00 +0000

Scalability Special Interest Group

SIG Scalability is responsible for defining and driving scalability goals for Kubernetes. We also coordinate and contribute to general system-wide scalability and performance improvements (not falling into the charter of other individual SIGs) by driving large architectural changes and finding bottlenecks, as well as provide guidance and consultations about any scalability and performance related aspects of Kubernetes.
We are actively working on finding and removing various scalability bottlenecks which should lead us towards pushing system’s scalability higher. This may include going beyond 5k nodes in the future - although that’s not our priority as of now, this is very deeply in our area of interest and we are happy to guide and collaborate on any efforts towards that goal as long as they are not sacrificing on overall Kubernetes architecture (by making it non-maintainable, non-understandable, etc.).

The charter defines the scope and governance of the Scalability Special Interest Group.

Meetings

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

Regular SIG Meeting: Thursdays at 18:30 UTC (bi-weekly (upcoming meeting dates )). Convert to your timezone .
- Meeting notes and Agenda .
- Meeting recordings .

Leadership

Chairs

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

Marcel Zieba (@marseel ), Isovalent
David (Mengqi) Yu (@mengqiy ), Amazon

Technical Leads

The Technical Leads of the SIG establish new subprojects, decommission existing subprojects, and resolve cross-subproject technical issues and decisions.

Shyam Jeedigunta (@shyamjvs ), Amazon
Wojciech Tyczynski (@wojtek-t ), Google

Emeritus Leads

Matt Matejczyk (@mm4tt )

Contact

Slack: #sig-scalability
Mailing list
Open Community Issues/PRs
GitHub Teams:
- @kubernetes/sig-scalability - General Discussion
- @kubernetes/sig-scalability-leads - Leads
- @kubernetes/sig-scalability-pr-reviews - PR Reviews
Steering Committee Liaison: Antonio Ojea (@aojea )

Subprojects

The following subprojects are owned by sig-scalability:

inference-perf

Described below

Owners:
- kubernetes-sigs/inference-perf/heads/main

kubernetes-scalability-and-performance-tests-and-validation

Described below

Owners:
- kubernetes/community/sig-scalability/processes
- kubernetes/kubernetes/test/e2e/scalability

kubernetes-scalability-bottlenecks-detection

Described below

Owners:
- kubernetes/community/sig-scalability/blogs

kubernetes-scalability-definition

Described below

Owners:
- kubernetes/community/sig-scalability/configs-and-limits
- kubernetes/community/sig-scalability/slos

kubernetes-scalability-governance

Described below

Owners:
- kubernetes/community/sig-scalability/governance

kubernetes-scalability-test-frameworks

Described below

Owners:

Scalability Regression - Contact Points

SIG Scalability has established best-effort oncall rotation operating in CEST/CET business hours (~9:00-18:00). If you have any inquiries about scalability regressions, e.g. regression status, whether it should block the release or not, etc. please reach out to the current oncaller. They can be found on https://go.k8s.io/oncall .

Also do not hesitate to contact those SIG members for status update:

Antoni Zawody (@tosi3k ), Google
Jakub Przychodzeń (@jprzychodzen ), Google
Maciej Borsz (@mborsz ), Google
Marcel Zięba (@marseel ), Google
Wojciech Tyczynski (@wojtek-t ), Google

Upcoming Meeting Dates

Check out this calendar for upcoming meeting dates.

You can use this link to add it to your personal Google calendar.

Details about SIG-Scalability sub-projects

Kubernetes scalability definition

Defining what does it mean that “Kubernetes scales”. This includes defining (or approving) individual performance and scalability related SLIs/SLOs, ensuring they are all oriented on user experience and consistent with each other.

Measuring and publishing limits within which Kubernetes is supposed to scale as defined above and providing recommendations about setting clusters in scalable and performant ways.

Kubernetes Scalability SLIs/SLOs .

Kubernetes scalability governance

Establishing and documenting best practises on how do design and implement Kubernetes features in scalable and performance way. Educating contributors and ensuring best practises are widely used.

Kubernetes scalability bottlenecks detection

Detecting scalability bottlenecks and limitations, documenting them and driving architectural changes to eliminate those (if such are required) in collaboration with other SIGs or directly delegating non cross-cutting improvements to individual SIGs.

Scalability issues with Services

Kubernetes scalability test frameworks

Designing and creating frameworks to make scalability and performance testing of Kubernetes easy and available for all contributors. Different frameworks may help in different aspects of scalability testing, enabling making conscious tradeoffs, e.g. cost vs accuracy or real life vs more generalized benchmarking scenarios.

Kubernetes scalability and performance tests and validation

Ensuring that all tests necessary to validate Kubernetes scalability and performance exists (ideally by providing easy-to-use frameworks and working with SIGs to provide them), having environment and resources to run them:

Ensuring that tests are being executed according to calendar and ensuring that each official Kubernetes release satisfies all scalability and performance requirements as stated in “Kubernetes scalability” definition. This also includes designing processes to reduce maintenance work and number of scalability and performance regressions:

Processes

Inference perf

Inference Perf is a GenAI inference performance benchmarking tool that allows you to benchmark and analyze the performance of inference deployments. It is agnostic of model servers and can be used to measure performance and compare different systems apples-to-apples.

Community: SIG Scheduling

Mon, 01 Jan 0001 00:00:00 +0000

Scheduling Special Interest Group

SIG Scheduling is responsible for the components that make Pod placement decisions.

The charter defines the scope and governance of the Scheduling Special Interest Group.

Meetings

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

biweekly meeting (Asia & Europe): Tuesdays at 9:00 CET (Central European Time) (biweekly starting Tuesday Feb 11, 2025). Convert to your timezone .
- Meeting notes and Agenda .
- Meeting recordings .
biweekly meeting (NA & Europe): Thursdays at 9:00 PT (Pacific Time) (biweekly starting Thursday June 7, 2018). Convert to your timezone .
- Meeting notes and Agenda .
- Meeting recordings .
descheduler biweekly meeting Europe time: Tuesdays at 14:30 CET (Central European Time) (biweekly starting Tuesday Feb 27, 2024). Convert to your timezone .
- Meeting notes and Agenda .
- Meeting recordings .
descheduler biweekly meeting North America time: Tuesdays at 19:30 CET (Central European Time) (biweekly starting Tuesday March 12, 2024). Convert to your timezone .
- Meeting notes and Agenda .
- Meeting recordings .

Leadership

Chairs

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

Maciej Skoczeń (@macsko ), Google
Kensei Nakada (@sanposhiho ), Independent

Technical Leads

The Technical Leads of the SIG establish new subprojects, decommission existing subprojects, and resolve cross-subproject technical issues and decisions.

Dominik Marciński (@dom4ha ), Google
Kensei Nakada (@sanposhiho ), Independent

Emeritus Leads

Wei Huang (@Huang-Wei )
Abdullah Gharaibeh (@ahg-g )
Aldo Culquicondor (@alculquicondor )
Bobby (Babak) Salamat (@bsalamat )
Klaus Ma (@k82cn )

Contact

Slack: #sig-scheduling
Mailing list
Open Community Issues/PRs
GitHub Teams:
- @kubernetes/sig-scheduling-leads - SIG Scheduling leads
- @kubernetes/sig-scheduling-misc - General Discussion
Steering Committee Liaison: Benjamin Elder (@BenTheElder )

Working Groups

The following working groups are sponsored by sig-scheduling:

Subprojects

The following subprojects are owned by sig-scheduling:

cluster-capacity

Owners:
- kubernetes-sigs/cluster-capacity

descheduler

Owners:
- kubernetes-sigs/descheduler

dra-driver-topology

Owners:
- kubernetes-sigs/dra-driver-topology

kube-scheduler-simulator

Owners:
- kubernetes-sigs/kube-scheduler-simulator

kube-scheduler-wasm-extension

Owners:
- kubernetes-sigs/kube-scheduler-wasm-extension

kueue

Leads:
- Michał Woźniak (@mimowo ), Google
- Yuki Iwai (@tenzen-y ), CyberAgent, Inc.
Owners:
- kubernetes-sigs/kueue

kwok

Owners:
- kubernetes-sigs/kwok

scheduler

Owners:
- kubernetes/kubernetes/cmd/kube-scheduler
- kubernetes/kubernetes/pkg/scheduler

scheduler-library

Owners:
- kubernetes-sigs/scheduler-library

scheduler-plugins

Owners:
- kubernetes-sigs/scheduler-plugins

Community: SIG Security

Mon, 01 Jan 0001 00:00:00 +0000

Security Special Interest Group

SIG Security takes a community-building approach to improving security for end users, project maintainers, and the Kubernetes project itself. We work collaboratively across SIGs to advance security-related features, write and update documentation, and maintain security processes and tools for the benefit of all.

The charter defines the scope and governance of the Security Special Interest Group.

Meetings

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

Regular SIG Meeting: Fridays at 8:00 PT (Pacific Time) (biweekly). Convert to your timezone .
- Meeting notes and Agenda .
- Meeting recordings .

Leadership

Chairs

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

Ian Coldwater (@IanColdwater ), Independent
Cailyn Edwards (@cailyn-codes ), Okta
Tabitha Sable (@tabbysable ), Datadog

Contact

Slack: #sig-security
Mailing list
Open Community Issues/PRs
GitHub Teams:
- @kubernetes/sig-security-leads - SIG Security Leads
- @kubernetes/sig-security-pr-reviews - SIG Security PR review notifications
Steering Committee Liaison: Kat Cosgrove (@katcosgrove )

Subprojects

The following subprojects are owned by sig-security:

security-audit

Third Party Security Audit

Owners:
- kubernetes/sig-security/sig-security-external-audit

security-docs

Security Documents and Documentation

Owners:
- kubernetes/sig-security/sig-security-docs
Contact:
- Slack: #sig-security-docs

security-self-assessments

Security self-assessments for K8s subprojects

Owners:
- kubernetes/sig-security/sig-security-assessments
Contact:
- Slack: #sig-security-assessments

security-tooling

Development and Enhancements of Security Tooling

Owners:
- kubernetes-sigs/cve-feed-osv
- kubernetes/sig-security/sig-security-tooling
Contact:
- Slack: #sig-security-tooling

sig-security

SIG Security discussions, documents, processes and other artifacts

Owners:
- kubernetes/sig-security
Contact:
- Slack: #sig-security

Community: SIG Storage

Mon, 01 Jan 0001 00:00:00 +0000

Storage Special Interest Group

SIG Storage is responsible for ensuring that different types of file and block storage (whether ephemeral or persistent, local or remote) are available wherever a container is scheduled (including provisioning/creating, attaching, mounting, unmounting, detaching, and deleting of volumes), storage capacity management (container ephemeral storage usage, volume resizing, etc.), influencing scheduling of containers based on storage (data gravity, availability, etc.), and generic operations on storage (snapshoting, etc.).

The charter defines the scope and governance of the Storage Special Interest Group.

Meetings

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

Regular CSI Implementation Meeting: Mondays at 10:00 PT (Pacific Time) (weekly). Convert to your timezone .
- Meeting notes and Agenda .
Regular SIG Issue Triage Meeting: Wednesdays at 10:00 PT (Pacific Time) (weekly). Convert to your timezone .
- Meeting notes and Agenda ).
Regular SIG Meeting: Thursdays at 9:00 PT (Pacific Time) (biweekly). Convert to your timezone .
- Meeting notes and Agenda .
- Meeting recordings .

Leadership

Chairs

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

Saad Ali (@saad-ali ), Google
Xing Yang (@xing-yang ), VMware

Technical Leads

The Technical Leads of the SIG establish new subprojects, decommission existing subprojects, and resolve cross-subproject technical issues and decisions.

Jan Šafránek (@jsafrane ), Red Hat
Michelle Au (@msau42 ), Google

Emeritus Leads

Bradley Childs (@childsb )

Contact

Slack: #sig-storage
Mailing list
Open Community Issues/PRs
GitHub Teams:
- @kubernetes/sig-storage-api-reviews - API Changes and Reviews
- @kubernetes/sig-storage-bugs - Bug Triage and Troubleshooting
- @kubernetes/sig-storage-feature-requests - Feature Requests
- @kubernetes/sig-storage-misc - General Discussion
- @kubernetes/sig-storage-pr-reviews - PR Reviews
- @kubernetes/sig-storage-proposals - Design Proposals
- @kubernetes/sig-storage-test-failures - Test Failures and Triage
Steering Committee Liaison: Paco Xu 徐俊杰 (@pacoxu )

Working Groups

The following working groups are sponsored by sig-storage:

Subprojects

The following subprojects are owned by sig-storage:

external-snapshot-metadata

Owners:
- kubernetes-csi/external-snapshot-metadata

external-storage

Owners:
- kubernetes-sigs/sig-storage-lib-external-provisioner
- kubernetes-sigs/sig-storage-local-static-provisioner

git-sync

Owners:
- kubernetes/git-sync

gluster-provisioner

Owners:
- kubernetes-sigs/gluster-block-external-provisioner
- kubernetes-sigs/gluster-file-external-provisioner

kubernetes-cosi

Owners:
- kubernetes-sigs/container-object-storage-interface
- kubernetes-sigs/cosi-driver-sample
Contact:
- Slack: #sig-storage-cosi

kubernetes-csi

Owners:

mount-utils

Owners:
- kubernetes/kubernetes/staging/src/k8s.io/mount-utils

nfs-provisioner

Owners:
- kubernetes-sigs/nfs-ganesha-server-and-external-provisioner
- kubernetes-sigs/nfs-subdir-external-provisioner

volume-populators

Owners:
- kubernetes-csi/lib-volume-populator
- kubernetes-csi/volume-data-source-validator

volumes

Owners:
- kubernetes/kubernetes/pkg/volume

Details

The Kubernetes Storage Special-Interest-Group (SIG) is a working group within the Kubernetes contributor community interested in storage and volume plugins.

Meeting

We hold a public meeting every two weeks, on Thursdays at 9 AM (PT).

Agenda and any notes from each meeting are captured in this document .
Copy the meeting invite from the Shared SIG Storage Calendar .
Recordings of past meetings: https://www.youtube.com/playlist?list=PLb1_clREIGYVaqvKaUsVyXxjfcSQDBnmB

Contributing

Interested in contributing to storage features in Kubernetes? Please read our guide for new contributors

Community: SIG Testing

Mon, 01 Jan 0001 00:00:00 +0000

Testing Special Interest Group

Interested in how we can most effectively test Kubernetes. We’re interested specifically in making it easier for the community to run tests and contribute test results, to ensure Kubernetes is stable across a variety of cluster configurations and cloud providers.

The charter defines the scope and governance of the Testing Special Interest Group.

Meetings

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

Hydrophone Office Hours: Tuesdays at 13:00 PT (Pacific Time) (bi-weekly starting Tuesday April 16, 2024). Convert to your timezone .
SIG Testing Bi-Weekly Meeting: Tuesdays at 10:00 PT (Pacific Time) (bi-weekly starting Tuesday August 13, 2019). Convert to your timezone .
- Meeting notes and Agenda .
- Meeting recordings .

Leadership

Chairs

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

Brady Pratt (@jbpratt ), Red Hat
Michelle Shepardson (@michelle192837 ), Google
Brian McQueen (@xmcqueen ), LinkedIn

Technical Leads

The Technical Leads of the SIG establish new subprojects, decommission existing subprojects, and resolve cross-subproject technical issues and decisions.

Benjamin Elder (@BenTheElder ), Google
Antonio Ojea (@aojea ), Google
Patrick Ohly (@pohly ), Intel

Emeritus Leads

Alvaro Aleman (@alvaroaleman )
Cole Wagner (@cjwagner )
Erick Fejta (@fejta )
Aaron Crickenberger (@spiffxp )
Steve Kuznetsov (@stevekuznetsov )
Timothy St. Clair (@timothysc )

Contact

Slack: #sig-testing
Mailing list
Open Community Issues/PRs
GitHub Teams:
- @kubernetes/sig-testing - General Discussion
- @kubernetes/sig-testing-pr-reviews - PR Reviews
Steering Committee Liaison: Paco Xu 徐俊杰 (@pacoxu )

Subprojects

The following subprojects are owned by sig-testing:

Cloud Provider for KIND

Cloud provider for KIND clusters

Leads:
- Benjamin Elder (@BenTheElder ), Google
- Antonio Ojea (@aojea ), Google
Owners:
- kubernetes-sigs/cloud-provider-kind

boskos

Boskos is a resource manager service that handles different kinds of resources and transitions between different states. We use it on the Kubernetes project to manage pools of GCP projects for CI/CD.

Leads:
- Davanum Srinivas (@dims ), NVIDIA
- Mahamed Ali (@upodroid ), Cisco
Owners:
- kubernetes-sigs/boskos

e2e-framework

An experimental e2e testing framework for Kubernetes clusters.

Owners:
- kubernetes-sigs/e2e-framework

hydrophone

Hydrophone is a lightweight Kubernetes conformance tests runner

Leads:
- Davanum Srinivas (@dims ), NVIDIA
- Ricky Sadowski (@rjsadow ), ICR Team
Owners:
- kubernetes-sigs/hydrophone

kind

Kubernetes IN Docker. Run Kubernetes test clusters on your local machine using Docker containers as nodes.

Leads:
- Benjamin Elder (@BenTheElder ), Google
- Antonio Ojea (@aojea ), Google
Owners:
- kubernetes-sigs/kind
Contact:
- Slack: #kind

kubetest2

Kubetest2 is the framework for launching and running end-to-end tests on kubernetes. It is the next significant iteration of kubetest. We will be deprecating kubetest going forward.

Leads:
- Antonio Ojea (@aojea ), Google
- Mahamed Ali (@upodroid ), Cisco
Owners:
- kubernetes-sigs/kubetest2
- kubernetes/test-infra/kubetest

prow

Prow is a CI/CD system based on Kubernetes. See prow.k8s.io to see it in action for the Kubernetes project

Leads:
- Petr Muller (@petr-muller ), Red Hat
Owners:
- kubernetes-sigs/prow
Contact:
- Slack: #prow

randfill

Utility functions for filling types with randomized data (for kubernetes testing use).

Leads:
- Tim Hockin (@thockin ), Google
Owners:
- kubernetes-sigs/randfill

sig-testing

Home for SIG Testing discussion and documents.

Owners:
- kubernetes/sig-testing

test-infra

Miscellaneous tools and configuration to run the testing infrastructure for the Kubernetes project

Owners:
- kubernetes/test-infra

testgrid

Welcome to TestGrid, a highly-configurable, interactive dashboard for viewing your test results in a grid! This hosts Kubernetes-related projects for TestGrid (currently, the new frontend). See https://github.com/GoogleCloudPlatform/testgrid for the main repository (currently, backend components).

Leads:
- Michelle Shepardson (@michelle192837 ), Google
Owners:
- kubernetes-sigs/testgrid

testing-commons

[best-effort] The testing-commons subproject focuses on matters of code structure, layout, and execution of kubernetes/kubernetes test code. It is currently staffed on a best-effort basis; please bring discussions to the sig-testing slack channel or meeting. For historical context, please see the former testing-commons meeting agenda and archived testing-commons slack channel

Owners:
- kubernetes/kubernetes/test

Presentations

Title	Slides	Video	Speakers
KubeCon NA 2018 - SIG Testing Intro	Slides	Video	@spiffxp, @stevekuznetsov
KubeCon NA 2018 - SIG Testing Deep Dive	Slides	Video	@cjwagner, @Katharine
KubeCon NA 2018 - Behind Your PR: How Kubernetes Uses Kubernetes to Run Kubernetes CI	Slides	Video	@BenTheElder, @krzyzacy
KubeCon China 2018 - Intro: SIG Testing	Slides	Video	@krzyzacy, @jessiezcc
KubeCon EU 2019 - SIG Testing Intro	Slides	Video	@cjwagner, @AishSundar
KubeCon EU 2019 - SIG Testing Deep Dive	TBD	Video	@BenTheElder, @munnerz
KubeCon EU 2019 - Testing Your K8s Apps with Kind	TBD	Video	@BenTheElder, @munnerz
KubeCon NA 2019 - SIG Testing Intro	Slides	Video	@chases2, @fejta
KubeCon NA 2022 - SIG Testing: Intro And Updates	TBD	Video	@BenTheElder, @michelle192837, @chaodaiG, @aojea

Community: SIG UI

Mon, 01 Jan 0001 00:00:00 +0000

UI Special Interest Group

Covers all things UI related. Efforts are centered around Kubernetes Dashboard: a general purpose, web-based UI for Kubernetes clusters. It allows users to manage applications running in the cluster and troubleshoot them, as well as manage the cluster itself.

The charter defines the scope and governance of the UI Special Interest Group.

Leadership

Chairs

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

Sebastian Florek (@floreks ), Plural
Joaquim Rocha (@joaquimrocha ), Amutable
Shu Muto (@shu-mutou ), NEC

Emeritus Leads

Dan Romlein (@danielromlein )
Jeffrey Sica (@jeefy )
Marcin Maciaszczyk (@maciaszczykm )

Contact

Slack: #sig-ui
Mailing list
Open Community Issues/PRs
Steering Committee Liaison: Maciej Szulik (@soltysh )

Subprojects

The following subprojects are owned by sig-ui:

headlamp

Owners:
- kubernetes-sigs/headlamp/heads/main

Community: SIG Windows

Mon, 01 Jan 0001 00:00:00 +0000

Windows Special Interest Group

Focuses on supporting Windows Node and scheduling Windows containers on Kubernetes.

The charter defines the scope and governance of the Windows Special Interest Group.

Meetings

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

Backlog Refinement / Bug Triage Meeting: Thursdays at 12:30 Eastern Time (ET) (biweekly). Convert to your timezone .
Regular SIG Meeting: Tuesdays at 12:30 Eastern Time (ET) (weekly). Convert to your timezone .
- Meeting notes and Agenda .
- Meeting recordings .
Weekly CI Meeting: Tuesdays at 12:15 Eastern Time (ET) (weekly). Convert to your timezone .
- Meeting notes and Agenda .

Leadership

Chairs

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

Aravindh Puthiyaparambil (@aravindhp ), Softdrive Technologies Group Inc.
Mark Rossetti (@marosset ), Microsoft

Technical Leads

The Technical Leads of the SIG establish new subprojects, decommission existing subprojects, and resolve cross-subproject technical issues and decisions.

Claudiu Belu (@claudiubelu ), Cloudbase Solutions
Mark Rossetti (@marosset ), Microsoft
Yuanliang Zhang (@zylxjtu ), Microsoft

Emeritus Leads

Patrick Lang (@PatrickLang )
Ben Moss (@benmoss )
Deep Debroy (@ddebroy )
Jay Vyas (@jayunit100 )
James Sturtevant (@jsturtevant )
Amim Knabben (@knabben )
Michael Michael (@michmike )

Contact

Slack: #sig-windows
Mailing list
Open Community Issues/PRs
GitHub Teams:
- @kubernetes/sig-windows-bugs - Bug Triage and Troubleshooting
- @kubernetes/sig-windows-feature-requests - Feature Requests
- @kubernetes/sig-windows-misc - General Discussion
Steering Committee Liaison: Benjamin Elder (@BenTheElder )

Subprojects

The following subprojects are owned by sig-windows:

windows-gmsa

Owners:
- kubernetes-sigs/windows-gmsa

windows-operational-readiness

Owners:
- kubernetes-sigs/windows-operational-readiness

windows-samples

Owners:
- kubernetes-sigs/sig-windows-samples

windows-service-proxy

Owners:
- kubernetes-sigs/windows-service-proxy

windows-testing

Owners:
- kubernetes-sigs/windows-testing

windows-tools

Owners:
- kubernetes-sigs/sig-windows-dev-tools
- kubernetes-sigs/sig-windows-tools

Getting Started

If you’re looking for information on building and running containers on Windows, you can get started at http://aka.ms/windowscontainers .

Kubernetes 1.14 includes stable support for Windows Server containers and has up-to-date documentation .

Additional information and guides are available in the KEPs for SIG-Windows

Discuss

Join us on Slack or the Kubernetes Community Forums to chat about Windows containers on Kubernetes.

Contributing

To get yourself familiar with contributing, please read the Kubernetes Contributor Guide and the SIG-Windows Contributor guide

We’re currently using a GitHub project in the weekly SIG-Windows meeting to track items with active progress for each release. That’s a great place to start to get the most up-to-date status, then feel free to join us on the Slack channel anytime with questions.

As always, you can also find the active list of open issues and proposals Open Code Issues and PRs for SIG/Windows on GitHub.

Meeting Recordings

Past meetings are in the Recorded Meetings Playlist on Youtube

Kubernetes Contributors – Special Interest Groups (SIGs)

Community: SIG API Machinery

API Machinery Special Interest Group

Meetings

Leadership

Chairs

Technical Leads

Contact

Subprojects

cel-admission-webhook

component-base

control-plane-features

crdify

idl-schema-client-pipeline

json

kube-api-linter

kubernetes-clients

server-api-aggregation

server-binaries

server-crd

server-frameworks

server-sdk

universal-machinery

yaml

Additional links

Community: SIG Apps

Apps Special Interest Group

Meetings

Leadership

Chairs

Technical Leads

Emeritus Leads

Contact

Working Groups

Subprojects

agent-devops

agent-sandbox

application

examples

execution-hook

kjob

kompose

workloads-api

Goals

Non-goals

Helm and Charts

Community: SIG Architecture

Architecture Special Interest Group

Meetings

Leadership

Chairs

Contact

Working Groups

Subprojects

admission-policies

ai-conformance

apisnoop

architecture-and-api-governance

code-organization

conformance-definition

enhancements

maintainer-tools

production-readiness

wg-device-management

Details about SIG-Architecture sub-projects

Architecture and API Governance

Enhancement Proposals

Conformance Definition

Code Organization

Production Readiness

Community: SIG Auth

Auth Special Interest Group

Meetings

Leadership

Chairs

Technical Leads

Emeritus Leads

Contact

Working Groups

Subprojects