Skip to content

Charter updates for SIG Cloud Provider #8522

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
14 changes: 10 additions & 4 deletions sig-cloud-provider/CHARTER.md
Original file line number Diff line number Diff line change
Expand Up @@ -11,27 +11,33 @@ SIG Cloud Provider’s mission is to simplify, develop, and maintain cloud provi

#### Areas of Focus

- Extension points between Kubernetes and any cloud provider
- Cloud provider specific integrations and extension points that are not already covered by a more specific SIG such as storage or networking.
- APIs/interfaces for efficiently provisioning/de-provisioning cloud resources (nodes, routes, load balancers, etc)
- Configuration of cluster components to enable cloud provider integrations
- Testing and testing frameworks to ensure vendor neutrality across all cloud providers

#### Code, Binaries and Services

The SIG offers standardization across cloud-provider-* repos that are owned by the SIG. We establish basic structure and tooling expectations to help new contributors to understand the code and how to contribute.

- the [common interfaces](https://github.com/kubernetes/cloud-provider/blob/master/cloud.go) consumed by all cloud providers
- the [cloud-controller-manager](https://github.com/kubernetes/kubernetes/tree/master/cmd/cloud-controller-manager), which acts as the “out-of-tree” cloud provider component for clusters.
- core controllers (started by the cloud-controller-manager) that interact with cloud provider resources
- all [cloud provider repositories](https://github.com/kubernetes?utf8=%E2%9C%93&q=cloud-provider-&type=&language=) under the Kubernetes organization
- [e2e tests for cloud provider specific](https://github.com/kubernetes/kubernetes/tree/master/test/e2e/cloud) functionality
- the subproject [apiserver-network-proxy](https://github.com/kubernetes-sigs/apiserver-network-proxy), which is an extensible system which controls network traffic from the Kube API Server.
- all the subprojects formerly owned by [SIG-AWS](https://github.com/kubernetes/community/tree/master/sig-aws#subprojects), [SIG-AZURE](https://github.com/kubernetes/community/tree/master/sig-azure#subprojects), [SIG-GCP](https://github.com/kubernetes/community/tree/master/sig-gcp#subprojects), [SIG-IBMCloud](https://github.com/kubernetes/community/tree/master/sig-ibmcloud#subprojects), [SIG-Openstack](https://github.com/kubernetes/community/tree/master/sig-openstack#subprojects), [SIG-VMware](https://github.com/kubernetes/community/tree/master/sig-vmware#subprojects).
- any new subproject that is cloud provider specific, unless there is another SIG already sponsoring it.

#### Cross-cutting and Externally Facing Processes

- This SIG works with SIG Testing & SIG Release to ensure that cloud providers are actively testing & reporting test results to testgrid.
- This SIG works with SIG Docs to provide user-facing documentation on configuring Kubernetes clusters with cloud provider integration enabled.
- This SIG works with new cloud providers in the ecosystem that want to host their code in the Kubernetes organization and have an interest in contributing back.
- This SIG actively engages with SIGs owning other external components of Kubernetes (CNI, CSI, etc) to ensure a consistent integration story for users.
- This SIG works with new cloud providers in the ecosystem that want to host their code in the kubernetes-sigs organization and have an interest in contributing back.
- A portion of the apiserver-network-proxy code needs to be compiled into the apiserver, which overlaps with SIG API Machinery.
- This SIG actively engages with SIGs owning other external components of Kubernetes (CNI, CSI, other networking and storage, apiserver, and similar) to ensure a consistent integration story for users.
- This SIG collaborates to create infrastructure-specific endpoints and extensions. This can entail participation in working groups or sponsorship of subprojects.
- This SIG participates in cross-SIG working groups, such as the node lifecycle working group.

### Out of scope

Expand All @@ -40,7 +46,7 @@ SIG Cloud Provider’s mission is to simplify, develop, and maintain cloud provi

## Roles and Organization Management

This sig follows adheres to the Roles and Organization Management outlined in [sig-governance]
This SIG adheres to the Roles and Organization Management outlined in [sig-governance]
and opts-in to updates and modifications to [sig-governance].

### Additional responsibilities of Chairs
Expand Down