Community: Transition all SIG-{cloud provider} to WG-{cloud-provider} under SIG-Cloud-Provider

[hogepodge]

Under the charter of the recently founded SIG-Cloud-Provider, global code ownership will transition from individual cloud sigs to sub-projects (or working groups) within SIG-Cloud-Provider.

Tracking issue for this work.

https://github.com/kubernetes/community/blob/master/sig-cloud-provider/CHARTER.md#subprojects--areas-of-focus

/sig-cloud-provider
/sig-aws
/sig-azure
/sig-gcp
/sig-ibmcloud
/sig-openstack
/sig-vmware

[hogepodge]

/sig cloud-provider
/sig aws
/sig azure
/sig gcp
/sig ibmcloud
/sig openstack
/sig vmware

[fejta-bot]

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle stale

[nikhita]

/remove-lifecycle stale

[hogepodge]

In recent discussions with SIG-Cloud-Provider participants at KubeCon Seattle, it was indicated that many providers would like to keep their SIGS, or SIG-like structures, intact for further cross-SIG development and user support. This will be an ongoing topic of discussion and we can use this as a tracking issue for it.

[hogepodge]

/assign @hogepodge @andrewsykim @jagosan

[d-nishi]

@hogepodge we discussed the idea of sub sigs under sig cloud provider.

Is that discussion being moved forward?

[hogepodge]

The discussion will be moving forward, no decision has been made on any particular course of action yet.

[andrewsykim]

I'm working on a proposal that will be reviewed by steering committee, but would be great to get everyone in the SIG (and other provider SIGs) to review first :).

[d-nishi]

@andrewsykim let’s work together on the proposal if that’s fine by you. Would love to help!

[andrewsykim]

Sounds good! I'll share a template of it soon :)

[hogepodge]

/assign @d-nishi

[justaugustus]

@andrewsykim -- happy to review as well!
/assign

[hogepodge]

@andrewsykim do we have a template to share for this yet?

[GeetikaBatra]

@hogepodge and @chrigl is this related to these two: https://github.com/kubernetes/cloud-provider-openstack and https://github.com/kubernetes/kubernetes/blob/master/pkg/cloudprovider/providers/openstack

I see two places where the cloud providers reside. Also, I see that https://github.com/kubernetes/kubernetes/blob/master/pkg/cloudprovider/providers/openstack lacks some tests. If that's okay I would like to take it up.

[andrewsykim]

@GeetikaBatra yes, this effort is related to that.

Regarding test in the open stack provider, we can probably discuss that in a separate issue. I've created one here https://github.com/kubernetes/kubernetes/issues/74894 and pinged the appropriate people

[fejta-bot]

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle stale

[justaugustus]

/remove-lifecycle stale

[justaugustus]

/lifecycle frozen

[justaugustus]

Consolidation Tracking

Prerequisites for SIG Retirement

• [x] (@andrewsykim / @d-nishi) SIG’s retirement decision follows the decision making and communication processes as outlined in their charter - https://github.com/kubernetes/steering/issues/65

SIG Cloud Provider:

• [x] (@andrewsykim / @d-nishi) Send an email to [email protected] and [email protected] alerting the community of your intentions to disband or merge.

Mailing lists

• [ ] (former SIG Chairs) Rename the member mailing lists to kubernetes-provider-<provider>@googlegroups.com
• [ ] (former SIG Chairs) Archive the lead/chair mailing lists

Slack

• [x] (@andrewsykim) Rename Slack channels - https://github.com/kubernetes/community/pull/3895

Zoom

• [x] (Zoom admins) Deactivate the zoom licenses

Calendars

• [ ] (@andrewsykim) Grant former Chairs/TLs edit access to SIG Cloud Provider calendar
• [ ] (former SIG Chairs) Migrate provider meetings to SIG Cloud Provider
• [ ] (former SIG Chairs) Delete former SIG calendar

YouTube

• [x] (former SIG Chairs) Ensure that all SIG meetings to date are uploaded to YouTube

k/community

• [x] (@andrewsykim / @justaugustus) Move existing SIG directories in kubernetes/community
  
  
  
  • https://github.com/kubernetes/community/pull/3895
  
  
  • tombstones: https://github.com/kubernetes/community/pull/3941
  
  

GitHub

• [x] (@andrewsykim) Each subproject a SIG owns must transfer ownership to a new SIG, outside the project, or be retired - https://github.com/kubernetes/community/pull/3895
• [ ] (@justaugustus) Retire or transfer any test-infra jobs or testgrid dashboards, if applicable, owned by the SIG. Work with SIG Testing on this.
  
  
  
  • [x] Move existing k/k jobs - https://github.com/kubernetes/test-infra/pull/13703
  
  
  • [ ] Reconfigure dashboards/annotations
  
  
• [x] (@nikhita) Migrate/Remove/Deprecate any SIG/WG labels in labels.yaml - https://github.com/kubernetes/test-infra/pull/13677
• [x] (@justaugustus) Remove or rename any GitHub teams that refer to the SIG - https://github.com/kubernetes/org/pull/1052
• [x] (@andrewsykim / @justaugustus) Update sigs.yaml to remove or rename
  
  
  
  • https://github.com/kubernetes/community/pull/3895
  
  
  • https://github.com/kubernetes/community/pull/3941
  
  
  • https://github.com/kubernetes/org/pull/1052
  
  

[mrbobbytables]

I think all the tasks have been completed outside of the remaining ML / Zoom / Calendar tasks.

[mrbobbytables]

Jorge and I will finish the tasks out on this one.
/assign @castrojo @mrbobbytables
/remove-lifecycle frozen

[fejta-bot]

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle stale

[fejta-bot]

Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle rotten

[mrbobbytables]

I believe all AIs have been completed, going to go ahead and close this issue for now.

/close

[k8s-ci-robot]

@mrbobbytables: Closing this issue.

In response to this:

I believe all AIs have been completed, going to go ahead and close this issue for now.

/close

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.