Skip to content
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.

Sign up for GitHub

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

Jump to bottom

[Umbrella Issue] Migrate CNCF Ecosystem projects from k8s.gcr.io to registry.k8s.io #4780

Open
36 of 70 tasks
mrbobbytables opened this issue Feb 16, 2023 · 36 comments · Fixed by open-policy-agent/gatekeeper#2588, open-policy-agent/gatekeeper-library#295, coredns/helm#95, k3s-io/kine#161 or karmada-io/website#310
Open
36 of 70 tasks

[Umbrella Issue] Migrate CNCF Ecosystem projects from k8s.gcr.io to registry.k8s.io #4780

mrbobbytables opened this issue Feb 16, 2023 · 36 comments · Fixed by open-policy-agent/gatekeeper#2588, open-policy-agent/gatekeeper-library#295, coredns/helm#95, k3s-io/kine#161 or karmada-io/website#310
Labels
good first issue Denotes an issue ready for a new contributor, according to the "help wanted" guidelines.

Comments

@mrbobbytables
Copy link
Member

mrbobbytables commented Feb 16, 2023 •
edited
Loading

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
@castrojo castrojo mentioned this issue Feb 16, 2023
Merged
@austinlparker austinlparker mentioned this issue Feb 16, 2023
Closed
@JorTurFer JorTurFer mentioned this issue Feb 16, 2023
Merged
1 task
This was referenced Feb 16, 2023
Merged
Merged
@akshat5302
Copy link

Hey @mrbobbytables I would love to work on this umbrella issue and will try to migrate as much k8s.gcr.io to registry.k8s.io 👍

@dims
Copy link
Member

dims commented Feb 17, 2023

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

@mrbobbytables
Copy link
Member Author

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.

@aniruddha2000
Copy link

aniruddha2000 commented Feb 17, 2023 •
edited
Loading

I am currently looking at containerd, CoreDNS, CRI-O, Helm

@akshat5302
Copy link

I'm looking at Aeraki mesh,Akri, Antrea and Argo

This was referenced Feb 17, 2023
Closed
Merged
Merged
@harshitasao
Copy link

harshitasao commented Feb 17, 2023 •
edited
Loading

I'm looking at kubewarden, litmuschaos, karmada, KubeArmor, kubeEdge.

This was referenced Feb 17, 2023
Closed
Merged
Merged
@RishabhKodes
Copy link

Hi @dims @mrbobbytables, sent the pr's for kubevirt, meshery and thanosbench.

This was referenced Feb 17, 2023
Merged
Merged
Merged
Merged
@cpanato
Copy link
Member

cpanato commented Feb 17, 2023

Hello fro the Helm most of the changes are in the helm/charts repo, and that is archived so we will not change anything there.

the only change required is done in this PR helm/helm#11829

can you make that a check?

cc @mrbobbytables @jeefy

@cpanato cpanato mentioned this issue Feb 17, 2023
Merged
@mrbobbytables
Copy link
Member Author

Hello fro the Helm most of the changes are in the helm/charts repo, and that is archived so we will not change anything there.

the only change required is done in this PR helm/helm#11829

can you make that a check?

done 👍

This was referenced Feb 17, 2023
Closed
Merged
@shikharcodes
Copy link

shikharcodes commented Feb 17, 2023 •
edited
Loading

I'm currently looking at OpenEBS, VS Code Kubernetes Tools, WasmEdge Runtime, k8gb, knative.

@shikharcodes shikharcodes mentioned this issue Feb 17, 2023
Open
@DiptoChakrabarty
Copy link
Member

I am looking at k3s kudo and keptn and telepresence

This was referenced Apr 12, 2023
Merged
Closed
Merged
Merged
Merged
Merged
Merged
Merged
Closed
Closed
Merged
@ahmedwaleedmalik
Copy link

ahmedwaleedmalik commented Apr 12, 2023 •
edited
Loading

Hey folks, just an update:

Had to take over a few subtasks(organizations) since they were stalled for quite some time.

@ahmedwaleedmalik ahmedwaleedmalik mentioned this issue Apr 13, 2023
Merged
openshift-cherrypick-robot pushed a commit to openshift-cherrypick-robot/podman that referenced this issue Apr 18, 2023
@sohankunkerkar
*: migrate image registry to registry.k8s.io
74634a4 
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 <[email protected]>
@vinayak-kukreja vinayak-kukreja mentioned this issue May 16, 2023
Merged
mergify bot pushed a commit to cdk8s-team/cdk8s-core that referenced this issue May 16, 2023
@vinayak-kukreja
chore: migrate image registry to registry.k8s.io (#1207)
be39113 
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.
cdk8s-automation pushed a commit to cdk8s-team/cdk8s-core that referenced this issue May 16, 2023
@vinayak-kukreja
chore: migrate image registry to registry.k8s.io (#1207)
cdd4431 
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 <[email protected]>
dtfranz pushed a commit to dtfranz/operator-framework-rukpak that referenced this issue Jun 6, 2023
@awgreene @dtfranz
Move to the new Kubernetes image repository
6864b8d 
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 <[email protected]>
dtfranz pushed a commit to dtfranz/operator-framework-rukpak that referenced this issue Jun 6, 2023
@awgreene @dtfranz
Move to the new Kubernetes image repository
4d878be 
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 <[email protected]>
@thaJeztah thaJeztah mentioned this issue Jul 14, 2023
Merged
bpradipt pushed a commit to bpradipt/cloud-api-adaptor that referenced this issue Aug 12, 2023
@CIPHERTron @bpradipt
Fixes: kubernetes/k8s.io#4780
fc6982c 
Signed-off-by: CIPHERTron <[email protected]>
This was referenced Aug 22, 2023
Open
Open
Open
Open
wainersm pushed a commit to wainersm/cc-cloud-api-adaptor that referenced this issue Sep 5, 2023
@CIPHERTron @bpradipt
Fixes: kubernetes/k8s.io#4780
9b0f8c2 
Signed-off-by: CIPHERTron <[email protected]>
TomSweeneyRedHat pushed a commit to TomSweeneyRedHat/podman that referenced this issue Jul 20, 2024
@sohankunkerkar @TomSweeneyRedHat
[v4.4.1-rhel] *: migrate image registry to registry.k8s.io
cbe3e18 
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 <[email protected]>
@ameukam
Copy link
Member

ameukam commented Dec 9, 2024

@mrbobbytables are we still doing this ? If no maybe we can close ?

@BenTheElder
Copy link
Member

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
good first issue Denotes an issue ready for a new contributor, according to the "help wanted" guidelines.
Projects
None yet
Milestone
No milestone