Closed spiffxp closed 4 years ago
https://github.com/kubernetes/community/pull/1979 calls incubator deprecated
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
/remove-lifecycle stale
/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.
/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
/priority important-soon
i thought steering owned spartakus? https://github.com/kubernetes/community/tree/master/committee-steering
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).
@neolit123 I'm going off of what is currently listed in sigs.yaml and shows up in each SIG's README.md
:wave: Hey! I just opened this issue to kick off the migration of our ref-docs: https://github.com/kubernetes/org/issues/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!
descheduler has now been migrated to kubernetes-sigs ref: https://github.com/kubernetes/org/issues/1176
reference docs has now been migrated to kubernetes-sigs ref: https://github.com/kubernetes/org/issues/1158
Opened https://github.com/kubernetes/community/pull/4700 to suggest that the kubernetes-incubator/cluster-proportional* projects move to sig-network
/remove committee-steering
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)
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
There are a few things here in k/community that do need to be updated (mostly our github admin docs)
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?
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! :tada:
/close
@nikhita: Closing this issue.
/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: