Skip to content
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

Deprecate kubernetes-incubator in favor of kubernetes-sigs #1922

Closed
spiffxp opened this issue Mar 12, 2018 · 19 comments
Closed

Deprecate kubernetes-incubator in favor of kubernetes-sigs #1922

spiffxp opened this issue Mar 12, 2018 · 19 comments
Assignees
Labels
area/github-management Issues or PRs related to GitHub Management subproject committee/steering Denotes an issue or PR intended to be handled by the steering committee. lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness. priority/important-soon Must be staffed and worked on either currently, or very soon, ideally in time for the next release. sig/contributor-experience Categorizes an issue or PR as relevant to SIG Contributor Experience.
Milestone

Comments

@spiffxp
Copy link
Member

spiffxp commented Mar 12, 2018

/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
@k8s-ci-robot k8s-ci-robot added committee/steering Denotes an issue or PR intended to be handled by the steering committee. sig/contributor-experience Categorizes an issue or PR as relevant to SIG Contributor Experience. labels Mar 12, 2018
@spiffxp
Copy link
Member Author

spiffxp commented Apr 11, 2018

#1979 calls incubator deprecated

@fejta-bot
Copy link

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

@k8s-ci-robot k8s-ci-robot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Jul 10, 2018
@spiffxp
Copy link
Member Author

spiffxp commented Jul 16, 2018

/remove-lifecycle stale

@k8s-ci-robot k8s-ci-robot removed the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Jul 16, 2018
@spiffxp
Copy link
Member Author

spiffxp commented Aug 3, 2018

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

@k8s-ci-robot k8s-ci-robot added the lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness. label Aug 3, 2018
@spiffxp
Copy link
Member Author

spiffxp commented Jul 31, 2019

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

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

@k8s-ci-robot k8s-ci-robot added the area/github-management Issues or PRs related to GitHub Management subproject label Jul 31, 2019
@spiffxp
Copy link
Member Author

spiffxp commented Jul 31, 2019

/priority important-soon

@k8s-ci-robot k8s-ci-robot added the priority/important-soon Must be staffed and worked on either currently, or very soon, ideally in time for the next release. label Jul 31, 2019
@parispittman
Copy link
Contributor

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

@neolit123
Copy link
Member

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
Copy link
Member Author

spiffxp commented Aug 6, 2019

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

@jimangel
Copy link
Member

jimangel commented Sep 5, 2019

👋 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
Copy link
Member

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

@mrbobbytables
Copy link
Member

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

@mrbobbytables mrbobbytables modified the milestones: v1.18, v1.19 Feb 26, 2020
@spiffxp
Copy link
Member Author

spiffxp commented Apr 7, 2020

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

@parispittman
Copy link
Contributor

/remove committee-steering

@spiffxp
Copy link
Member Author

spiffxp commented Sep 30, 2020

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
Copy link
Member

mrbobbytables commented Sep 30, 2020

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
Copy link
Member

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
Copy link
Member

nikhita commented Oct 5, 2020

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
Copy link
Contributor

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/github-management Issues or PRs related to GitHub Management subproject committee/steering Denotes an issue or PR intended to be handled by the steering committee. lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness. priority/important-soon Must be staffed and worked on either currently, or very soon, ideally in time for the next release. sig/contributor-experience Categorizes an issue or PR as relevant to SIG Contributor Experience.
Projects
None yet
Development

No branches or pull requests

8 participants