Add SIG Cloud Provider #2201

andrewsykim · 2018-05-30T21:22:41Z

As discussed with @kubernetes/steering-committee. Discussion here.

I will be removing wg-cloud-provider related files in a follow up PR once everything for sig-cloud-provider is solidified.

andrewsykim · 2018-05-30T21:37:54Z

sig-cloud-provider/CHARTER.md

+    * Deployment tooling which has historically resided under [cluster/](https://github.com/kubernetes/kubernetes/tree/release-1.11/cluster)
+* Code ownership for all cloud providers that fall under the kubernetes organization and have opted to be subprojects of SIG Cloud Provider. Following the guidelines around subprojects we anticipate providers will have full autonomy to maintain their own repositories, however, official code ownership will still belong to SIG Cloud Provider.
+    * [cloud-provider-azure](https://github.com/kubernetes/cloud-provider-azure)
+    * [cloud-provider-gcp](https://github.com/kubernetes/cloud-provider-gcp)


cc @jagosan @calebamiles @abgworrall

andrewsykim · 2018-05-30T21:38:06Z

sig-cloud-provider/CHARTER.md

+* Code ownership for all cloud providers that fall under the kubernetes organization and have opted to be subprojects of SIG Cloud Provider. Following the guidelines around subprojects we anticipate providers will have full autonomy to maintain their own repositories, however, official code ownership will still belong to SIG Cloud Provider.
+    * [cloud-provider-azure](https://github.com/kubernetes/cloud-provider-azure)
+    * [cloud-provider-gcp](https://github.com/kubernetes/cloud-provider-gcp)
+    * [cloud-provider-openstack](https://github.com/kubernetes/cloud-provider-openstack)


cc @dims @hogepodge

+1 from me. cc @dklyle

andrewsykim · 2018-05-30T21:38:49Z

sig-cloud-provider/CHARTER.md

+    * [cloud-provider-azure](https://github.com/kubernetes/cloud-provider-azure)
+    * [cloud-provider-gcp](https://github.com/kubernetes/cloud-provider-gcp)
+    * [cloud-provider-openstack](https://github.com/kubernetes/cloud-provider-openstack)
+    * [cloud-provider-vsphere](https://github.com/kubernetes/cloud-provider-vsphere)


cc @frapposelli @tpepper

@andrewsykim How about cloud-provider-alicloud for now ? Should we add it here now ?

@andrewsykim , Additional comments for @aoxn , The cloud provider of Alibaba Cloud is in https://github.com/AliyunContainerService/alicloud-controller-manager and we hope it can be hosted under Kubernetes organization. Thanks

@andrewsykim I am also looking forward to getting the cloud-provider-alicloud into kubernetes community too. It will be much easier for users to setup and manage kubernetes on alicloud.

cc @aoxn @denverdino

The list of repos in the charter is the existing repos (belonging to existing SIGs) that would immediately fall under sig-cloud-provider ownership. Once the SIG is formed we will have a formal process in place for new providers :).

andrewsykim · 2018-05-30T21:39:16Z

sig-cloud-provider/CHARTER.md

+    * [cloud-controller-manager](https://github.com/kubernetes/kubernetes/tree/master/cmd/cloud-controller-manager)
+    * Deployment tooling which has historically resided under [cluster/](https://github.com/kubernetes/kubernetes/tree/release-1.11/cluster)
+* Code ownership for all cloud providers that fall under the kubernetes organization and have opted to be subprojects of SIG Cloud Provider. Following the guidelines around subprojects we anticipate providers will have full autonomy to maintain their own repositories, however, official code ownership will still belong to SIG Cloud Provider.
+    * [cloud-provider-azure](https://github.com/kubernetes/cloud-provider-azure)


cc @khenidak @shubheksha

andrewsykim · 2018-05-30T21:39:32Z

OWNERS_ALIASES

@@ -32,6 +32,10 @@ aliases:
    - soltysh
    - pwittrock
    - AdoHe
+  sig-cloud-provider-leads:
+    - andrewsykim
+    - jagosan


cc @jagosan @wlan0

As the author of the original charter, someone who's worked closely with the sig-docs and sig-testing teams, and has been an active participant in the group that has openly advocated to the benefit of all cloud providers, I would also like to be named as a co-lead in this sig.

+1 @hogepodge

Any concerns with deadlocks if the number of leads is even? How are decisions arbitrated?

Spoke with Jago and Sid, Sid (wlan0) plans to step down as chair (due to other obligations) so we should be good to have Chris onboard while also addressing @jdumars concerns around deadlocks.

hogepodge

Some additional comments about scope and leadership.

hogepodge · 2018-05-30T23:23:54Z

OWNERS_ALIASES

@@ -32,6 +32,10 @@ aliases:
    - soltysh
    - pwittrock
    - AdoHe
+  sig-cloud-provider-leads:
+    - andrewsykim
+    - jagosan


As the author of the original charter, someone who's worked closely with the sig-docs and sig-testing teams, and has been an active participant in the group that has openly advocated to the benefit of all cloud providers, I would also like to be named as a co-lead in this sig.

hogepodge · 2018-05-30T23:30:02Z

sig-cloud-provider/CHARTER.md

+The long term goal of SIG Cloud Provider is to promote a vendor neutral ecosystem for our community.  Vendors wanting to support Kubernetes should feel equally empowered to do so
+as any of today’s existing cloud providers; but more importantly ensuring a high quality user experience across providers. The SIG will act as a central group for developing
+the Kubernetes project in a way that ensures all providers share common privileges and responsibilities. Below are some concrete goals on how SIG Cloud Provider plans to accomplish this.
+


I would like us to add a section about advocacy that includes supporting provider working group meetings at events and other use of community resources. One of the large impacts this will have on the community is the potential loss of collaboration and meeting space at events.

SIG-OpenStack, for example, regularly has between 40-60 attendees at it's SIG meetings at KubeCon, and the loss of access to these resources will be one of the largest impacts our community will feel.

We spoke about this on slack, we'll be addressing this during the transitional period and add more details in the charter (or in a KEP) in the near future.

calebamiles · 2018-06-01T18:20:37Z

/assign

calebamiles · 2018-06-01T18:20:42Z

/approve

calebamiles · 2018-06-01T18:20:49Z

/lgtm

k8s-ci-robot · 2018-06-01T18:20:49Z

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: calebamiles

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

~~OWNERS~~ [calebamiles]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

Add SIG Cloud Provider

k8s-ci-robot added size/L Denotes a PR that changes 100-499 lines, ignoring generated files. cncf-cla: yes Indicates the PR's author has signed the CNCF CLA. labels May 30, 2018

k8s-ci-robot requested review from calebamiles and jbeda May 30, 2018 21:22

k8s-ci-robot added the sig/architecture Categorizes an issue or PR as relevant to SIG Architecture. label May 30, 2018

andrewsykim force-pushed the sig-cloud-provider branch from 49d993f to 8754509 Compare May 30, 2018 21:25

andrewsykim commented May 30, 2018

View reviewed changes

hogepodge suggested changes May 30, 2018

View reviewed changes

andrewsykim added 2 commits May 31, 2018 14:25

add sig-cloud-provider to sigs.yaml

ed8584f

add sig-cloud-provider charter

ccca239

andrewsykim force-pushed the sig-cloud-provider branch from 8754509 to 409bd64 Compare May 31, 2018 18:27

move wg-cloud-provider KEPs to sig-cloud-provider

e058f15

andrewsykim force-pushed the sig-cloud-provider branch from 409bd64 to e058f15 Compare May 31, 2018 18:31

k8s-ci-robot assigned calebamiles Jun 1, 2018

k8s-ci-robot added lgtm "Looks good to me", indicates that a PR is ready to be merged. approved Indicates a PR has been approved by an approver from all required OWNERS files. labels Jun 1, 2018

k8s-ci-robot merged commit d4bd6d7 into kubernetes:master Jun 1, 2018

jdumars mentioned this pull request Jun 24, 2018

Charters Meta-issue kubernetes/steering#31

Closed

calebamiles pushed a commit to calebamiles/community that referenced this pull request Sep 5, 2018

Merge pull request kubernetes#2201 from andrewsykim/sig-cloud-provider

f8c657b

Add SIG Cloud Provider

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Add SIG Cloud Provider #2201

Add SIG Cloud Provider #2201

andrewsykim commented May 30, 2018 •

edited

Loading

andrewsykim May 30, 2018

andrewsykim May 30, 2018

dims May 30, 2018

andrewsykim May 30, 2018

aoxn Jun 1, 2018

denverdino Jun 1, 2018

xlgao-zju Jun 1, 2018 •

edited

Loading

andrewsykim Jun 1, 2018 •

edited

Loading

andrewsykim May 30, 2018

andrewsykim May 30, 2018

hogepodge May 30, 2018

dims May 31, 2018

jdumars May 31, 2018

andrewsykim May 31, 2018

hogepodge left a comment

hogepodge May 30, 2018

hogepodge May 30, 2018

andrewsykim Jun 1, 2018 •

edited

Loading

calebamiles commented Jun 1, 2018

calebamiles commented Jun 1, 2018

calebamiles commented Jun 1, 2018

k8s-ci-robot commented Jun 1, 2018

Add SIG Cloud Provider #2201

Add SIG Cloud Provider #2201

Conversation

andrewsykim commented May 30, 2018 • edited Loading

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

xlgao-zju Jun 1, 2018 • edited Loading

Choose a reason for hiding this comment

andrewsykim Jun 1, 2018 • edited Loading

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

hogepodge left a comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

andrewsykim Jun 1, 2018 • edited Loading

Choose a reason for hiding this comment

calebamiles commented Jun 1, 2018

calebamiles commented Jun 1, 2018

calebamiles commented Jun 1, 2018

k8s-ci-robot commented Jun 1, 2018

andrewsykim commented May 30, 2018 •

edited

Loading

xlgao-zju Jun 1, 2018 •

edited

Loading

andrewsykim Jun 1, 2018 •

edited

Loading

andrewsykim Jun 1, 2018 •

edited

Loading