Deprecate kubernetes-incubator in favor of kubernetes-sigs

[spiffxp]

/committee steering
/sig contributor-experience
/assign
ref: kubernetes/test-infra#7184

We have https://github.com/kubernetes/community/blob/master/kubernetes-repositories.md sorta spelling out kubernetes-sigs, and we have https://github.com/kubernetes/community/blob/master/incubator.md spelling out kubernetes-incubator.

There's been lots of mailing list and meeting talk about deprecating incubator and instead using kubernetes-sigs as the way forward. But we're sorta lacking in official looking docs

I'd like to:

• add a note to incubator calling it deprecated
• add a note to our list of orgs calling out kuberentes-sigs in use
• spell out the process to get a new repo created in kubernetes-sigs
  • consensus from sig leads
  • (process debt cleanup) spell out subprojects owned by sig
  • e-mail steering committee asking for repo to be created
  • start repo based on kubernetes-template-project

[spiffxp]

#1979 calls incubator deprecated

[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

[spiffxp]

/remove-lifecycle stale

[spiffxp]

/lifecycle frozen
Bumping in recency as this came up during the most recent steering . More in the context of "when are we setting a deadline to move everything out of incubator". I still think the process isn't well documented, but we've had a lot of good recent examples to work with.

[spiffxp]

/area github-management
There are 15 repos left in kubernetes-incubator.

• kubernetes-incubator/apiserver-builder-alpha - sig-api-machinery (Migrating apiserver-builder-alpha to @kubernetes-sigs org#1094)
• kubernetes-incubator/bootkube - sig-cluster-lifecycle (Migrate bootkube to kubernetes-sigs org#1305)
• kubernetes-incubator/cluster-capacity - sig-scheduling (Migrate cluster-capacity to kubernetes-sigs org#1529)
• kubernetes-incubator/cluster-proportional-autoscaler - sig-network (Migrate kubernetes-incubator/cluster-proportional*-autoscaler to kubernetes-sigs org#1823)
• kubernetes-incubator/cluster-proportional-vertical-autoscaler - sig-network (Migrate kubernetes-incubator/cluster-proportional*-autoscaler to kubernetes-sigs org#1823)
• kubernetes-incubator/custom-metrics-apiserver - sig-instrumentation (Migrate custom-metrics-apiserver to kubernetes-sigs org#1597)
• kubernetes-incubator/descheduler - sig-scheduling (Migrate descheduler to kubernetes-sigs org#1176)
• kubernetes-incubator/external-dns - sig-network (Migrate external-dns to kubernetes-sigs org#1286)
• kubernetes-incubator/external-storage - sig-storage (Deprecate kubernetes-incubator/external-storage/ org#1563)
• kubernetes-incubator/ip-masq-agent - sig-network (Migrating ip-masq-agent to @kubernetes-sigs org#1154)
• kubernetes-incubator/kube-aws - sig-cluster-lifecycle ([REQUEST] Migrate kubernetes-incubator/kube-aws to kubernetes-sigs org#2004)
• kubernetes-incubator/metrics-server - sig-instrumentation (Migrate metrics-server to kubernetes-sigs org#1382)
• kubernetes-incubator/reference-docs - sig-docs (migrate kubernetes-incubator/reference-docs org#1158)
• kubernetes-incubator/rktlet - sig-node (Archive kubernetes-incubator/rktlet org#1488)
• kubernetes-incubator/spartakus - committee-steering (Retire kubernetes-incubator/spartakus org#1354)

The automation between these orgs is the same. I think it's time for us to reach out to the owning sigs and ask them to migrate or retire these repos

[spiffxp]

/priority important-soon

[parispittman]

i thought steering owned spartakus? https://github.com/kubernetes/community/tree/master/committee-steering

[neolit123]

kubernetes-incubator/kube-aws - sig-cluster-lifecycle

from the readme:
https://github.com/kubernetes-incubator/kube-aws#kubernetes-incubator

SIG: sig-aws

recently there was a discussion with the slack user dominic (can't find the link), who wanted to ask if the repo can be graduated out of incubator. sig cluster-lifecycle probably won't take the project as it overlaps with kops, but i cannot speak for the chairs.

on the other hand, Andrew Kim gave feedback that SIG Cloud Provider can potentially take it.
(sig-aws folded into sig-cloud-provider).

[spiffxp]

@neolit123 I'm going off of what is currently listed in sigs.yaml and shows up in each SIG's README.md

[jimangel]

👋 Hey! I just opened this issue to kick off the migration of our ref-docs: kubernetes/org#1158

I would like to wait until 1.16 goes out the door and have some docs folks review the permissions suggested... but we should be good to go after that!

[mrbobbytables]

descheduler has now been migrated to kubernetes-sigs
ref: kubernetes/org#1176

[mrbobbytables]

reference docs has now been migrated to kubernetes-sigs
ref: kubernetes/org#1158

[spiffxp]

Opened #4700 to suggest that the kubernetes-incubator/cluster-proportional* projects move to sig-network

[parispittman]

/remove committee-steering

[spiffxp]

https://cs.k8s.io/?q=kubernetes-incubator&i=nope&files=&repos= there are still many references, need a human to verify which of these shouldn't be renamed (history) vs. which should (or could)

[mrbobbytables]

If you remove the kubernetes-incubator/kube-aws repo from the list it looks like its a lot less. Quite a few in k/website blog posts which we can ignore

Massive Query URL

There are a few things here in k/community that do need to be updated (mostly our github admin docs)

[mrbobbytables]

I've created an issue on k/website wrt to updating references to incubator. With that out of the way, do you think we can go ahead and close this issue?

[nikhita]

I've created an issue on k/website wrt to updating references to incubator. With that out of the way, do you think we can go ahead and close this issue?

There were a few migrated repos in k-sigs that still referenced kubernetes-incubator. I have created issues (linked above) in each of these repos.

The repo maintainers can follow up on those separately. Going to close this issue! 🎉

/close

[k8s-ci-robot]

@nikhita: Closing this issue.

In response to this:

I've created an issue on k/website wrt to updating references to incubator. With that out of the way, do you think we can go ahead and close this issue?

There were a few migrated repos in k-sigs that still referenced kubernetes-incubator. I have created issues (linked above) in each of these repos.

The repo maintainers can follow up on those separately. Going to close this issue! 🎉

/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.