-
Notifications
You must be signed in to change notification settings - Fork 702
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
Migrate descheduler to kubernetes-sigs #1176
Comments
/cc @ravisantoshgudimetla , @aveshagarwal |
/assign |
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. |
@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:
|
@mrbobbytables Just wanted to make sure. Thanks for your help. |
Added @ravisantoshgudimetla and @aveshagarwal to kubernetes-sigs in #1179 once those 2 merge, I can move the repo over :) |
One slight hiccup -- it looks like the repo has some integrations with the openshift ci system that were setup early last year:
@ingvagabund Do you know if this integration is still needed? |
@mrbobbytables lemme check it out |
Looks like the |
Thanks for looking into that @ingvagabund. I'll remove the account and move forward with the migration. 👍 |
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: kubernetes/community#4085 The PR updating OWNERS & SECURITY contacts is here: |
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 |
@mrbobbytables: Closing this issue. In response to this:
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. |
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
The text was updated successfully, but these errors were encountered: