-
Notifications
You must be signed in to change notification settings - Fork 827
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
[Umbrella Issue] Migrate CNCF Ecosystem projects from k8s.gcr.io to registry.k8s.io #4780
[Umbrella Issue] Migrate CNCF Ecosystem projects from k8s.gcr.io to registry.k8s.io #4780
Comments
Hey @mrbobbytables I would love to work on this umbrella issue and will try to migrate as much |
No need to ask, pick a couple of projects, leave a note here, and file PRs with them. Leaving a note here will ensure will ensure folks won't end up duplicating work |
Just to echo what dims said, please feel free to take them on and reference this issue. One request for anyone tackling these issues is to please double check the changes. There are some things that a simple find/replace isn't quite the answer e.g. generated code. |
I am currently looking at containerd, CoreDNS, CRI-O, Helm |
I'm looking at Aeraki mesh,Akri, Antrea and Argo |
I'm looking at kubewarden, litmuschaos, karmada, KubeArmor, kubeEdge. |
Hi @dims @mrbobbytables, sent the pr's for |
Hello fro the the only change required is done in this PR helm/helm#11829 can you make that a check? |
done 👍 |
I'm currently looking at |
I am looking at |
This change is a part of the bigger umbrella issue: kubernetes/k8s.io#4780 Currently, we need this change to get in cri-o/cri-o#6742, which is failing in CI due to inconsistent vendoring. Signed-off-by: Sohan Kunkerkar <sohank2602@gmail.com>
Kubernetes has switched to `registry.k8s.io` as their default [image registry](kubernetes/k8s.io#4780). This PR is updating instances of old registry [k8s.gcr.io](http://k8s.gcr.io/) in our codebase.
Kubernetes has switched to `registry.k8s.io` as their default [image registry](kubernetes/k8s.io#4780). This PR is updating instances of old registry [k8s.gcr.io](http://k8s.gcr.io/) in our codebase. (cherry picked from commit be39113) Signed-off-by: Vinayak Kukreja <78971045+vinayak-kukreja@users.noreply.github.com>
Problem: The Kubernetes project is moving its images from the k8s.gcr.io registry to the registry.k8s.io registry and our project relies on one of the images being moved. More information can be found here: kubernetes/k8s.io#4780 Solution: Update the referenced image to point to the same image hosted at the new registry. Signed-off-by: Alexander Greene <greene.al1991@gmail.com>
Problem: The Kubernetes project is moving its images from the k8s.gcr.io registry to the registry.k8s.io registry and our project relies on one of the images being moved. More information can be found here: kubernetes/k8s.io#4780 Solution: Update the referenced image to point to the same image hosted at the new registry. Signed-off-by: Alexander Greene <greene.al1991@gmail.com>
Signed-off-by: CIPHERTron <pritish.samal918@gmail.com>
Signed-off-by: CIPHERTron <pritish.samal918@gmail.com>
This change is a part of the bigger umbrella issue: kubernetes/k8s.io#4780 Currently, we need this change to get in cri-o/cri-o#6742, which is failing in CI due to inconsistent vendoring. Signed-off-by: Sohan Kunkerkar <sohank2602@gmail.com>
@mrbobbytables are we still doing this ? If no maybe we can close ? |
Note: With the GRC team's help we are keeping a redirect in place for the immediate future, HOWEVER: users should switch to registry.k8s.io as soon as possible, it is the canonical host, k8s.gcr.io redirects there anyhow, and there's no guaranteed timeline for sustaining k8s.gcr.io, the redirect was initially meant as a temporary measure to ease the transition. See also: https://registry.k8s.io#stability and related docs. |
With the change to defaulting to registry.k8s.io as our image registry and the planned freeze in April, downstream projects in the CNCF ecosystem will likely be impacted.
Currently 70 of the other CNCF projects contain references to k8s.gcr.io, there seems to be a wide mix of usage from docs, to base images and CI.
Below is a list of projects that were surfaced in a "dumb" search for k8s.gcr.io, there may be valid references or false positives and they should be checked more closely and updated where possible.
Projects
The text was updated successfully, but these errors were encountered: