-
Notifications
You must be signed in to change notification settings - Fork 733
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 images in Dockerhub to GHCR #2446
Comments
/remove-label lifecyle/needs-triage |
@Electronic-Waste: The label(s) 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. |
/remove-label lifecycle/needs-triage |
@Electronic-Waste: The label(s) 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. |
What you would like to be added?
As @juliusvonkohout mentioned in kubeflow/manifests#3010, we need to migrate training-operator images to GHCR.
Here is the list:
And we should also move images related to Kubeflow Trainer V2 to GHCR, and modify the image build/push/pull scripts.
/cc @kubeflow/wg-training-leads @kubeflow/wg-manifests-leads @mahdikhashan @helenxie-bit @Doris-xm @truc0
Why is this needed?
Dockerhub put a limit to the pull usage: https://docs.docker.com/docker-hub/usage/pulls/
Love this feature?
Give it a 👍 We prioritize the features with most 👍
The text was updated successfully, but these errors were encountered: