Org: Migrate descheduler to kubernetes-sigs

[k82cn]

New Repo, Staging Repo, or migrate existing

migrate existing (https://github.com/kubernetes-incubator/descheduler/)

Requested name for new repository

descheduler

Which Organization should it reside

kubernetes-sigs

If not a staging repo, who should have admin access

@ravisantoshgudimetla , @aveshagarwal , @k82cn

If not a staging repo, who should have write access

@ravisantoshgudimetla , @aveshagarwal , @k82cn

If not a staging repo, who should be listed as approvers in OWNERS

@ravisantoshgudimetla , @aveshagarwal , @k82cn

If not a staging repo, who should be listed in SECURITY_CONTACTS

@ravisantoshgudimetla , @aveshagarwal , @k82cn

What should the repo description be

Descheduler, based on its policy, finds pods that can be moved and evicts them. Used to be rescheduler.

What SIG and subproject does this fall under in sigs.yaml

sig-scheduling

Approvals

https://groups.google.com/forum/#!topic/kubernetes-sig-scheduling/Zpj7t3v-6aY

Additional context for request

None

[k82cn]

/cc @ravisantoshgudimetla , @aveshagarwal
/cc @ahg-g for repo migration

[mrbobbytables]

/assign

[aveshagarwal]

Please make sure that after this migration, history remains intact (regarding commits, stars etc.) and https://github.com/kubernetes-incubator/descheduler redirects to the new repo location.

[mrbobbytables]

@aveshagarwal The full history will be left intact :)

A redirect is automatically put in place by GitHub (we don't have control over it).

If you want to take a look at a repo that has previously been moved, a recent example is the service-catalog:

• Request to move: https://github.com/kubernetes/org/issues/882
• kubernetes-sigs repo: https://github.com/kubernetes-sigs/service-catalog
• incubator repo (redirects): https://github.com/kubernetes-incubator/service-catalog

[aveshagarwal]

@mrbobbytables Just wanted to make sure. Thanks for your help.

[mrbobbytables]

Added @ravisantoshgudimetla and @aveshagarwal to kubernetes-sigs in #1179
Added teams for descheduler in #1180

once those 2 merge, I can move the repo over :)

[mrbobbytables]

One slight hiccup -- it looks like the repo has some integrations with the openshift ci system that were setup early last year:

• https://github.com/openshift/release/blob/master/ci-operator/jobs/kubernetes-incubator/descheduler/kubernetes-incubator-descheduler-master-presubmits.yaml
• https://github.com/openshift/release/pull/683

@ingvagabund Do you know if this integration is still needed?

[ingvagabund]

@mrbobbytables lemme check it out

[ingvagabund]

Looks like the ci-kubernetes-descheduler-e2e-gce jenkins job was completely abandoned in favor of KIND. The last time the JJ was ran was Dec 18, 2018. The job can be ignored. All the PRs that got merged since Jan 2019 no longer run the JJ.

[mrbobbytables]

Thanks for looking into that @ingvagabund. I'll remove the account and move forward with the migration. 👍

[mrbobbytables]

The repo has now been migrated to kubernetes-sigs/descheduler

The teams have been given their associated permissions.

The PR updating it's location in sigs.yaml is here: https://github.com/kubernetes/community/pull/4085

The PR updating OWNERS & SECURITY contacts is here:
https://github.com/kubernetes-sigs/descheduler/pull/179

[mrbobbytables]

All outstanding items have been completed. I'm going to go ahead and close the issue.

If you have any problems, feel free to reopen or ping me on slack 👍

/close

[k8s-ci-robot]

@mrbobbytables: Closing this issue.

In response to this:

All outstanding items have been completed. I'm going to go ahead and close the issue.

If you have any problems, feel free to reopen or ping me on slack 👍

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