Visitar URL original
[Umbrella Issue] Migrate CNCF Ecosystem projects from k8s.gcr.io to registry.k8s.io · Issue #4780 · kubernetes/k8s.io · GitHub
Skip to content

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

Open

Description

@mrbobbytables

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

Activity

  1. akshat5302 commented on Feb 17, 2023

    @akshat5302

    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 👍

  2. dims commented on Feb 17, 2023

    @dims
    Member

    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

  3. mrbobbytables commented on Feb 17, 2023

    @mrbobbytables
    MemberAuthor

    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.

  4. aniruddha2000 commented on Feb 17, 2023

    @aniruddha2000

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

  5. akshat5302 commented on Feb 17, 2023

    @akshat5302

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

  6. harshitasao commented on Feb 17, 2023

    @harshitasao

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

  7. RishabhKodes commented on Feb 17, 2023

    @RishabhKodes

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

  8. cpanato commented on Feb 17, 2023

    @cpanato
    Member

    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

  9. mrbobbytables commented on Feb 17, 2023

    @mrbobbytables
    MemberAuthor

    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 👍

  10. shikharcodes commented on Feb 17, 2023

    @shikharcodes

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

  11. DiptoChakrabarty commented on Feb 17, 2023

    @DiptoChakrabarty

    I am looking at k3s kudo and keptn and telepresence

  12. rayandas commented on Feb 17, 2023

    @rayandas
    Member

    I am looking at cert-manager, flux, kyverno, longhorn and OpenKruise

  13. kannon92 commented on Feb 17, 2023

    @kannon92
    Contributor

    Hello @mrbobbytables! Thank you for documenting these cases.

    I noticed that for Armada you are still using our old org domain and that issue points to a lot of code unrelated to Armada. We moved the Armada project to armadaproject org and I did the search and I did not find any references to k8s.gcr.io:

    https://github.com/search?q=org%3Aarmadaproject+%22k8s.gcr.io%22

    I think you could mark the Armada one as complete!

  14. mrbobbytables commented on Feb 17, 2023

    @mrbobbytables
    MemberAuthor

    Thanks @kannon92, I'll mark it off 👍

    I got the org from the CNCF's projects.csv doc here: https://github.com/cncf/toc/blob/main/docs/PROJECTS.csv

    It might be worth opening a PR to update it to reflect its current location.

  15. 32 remaining items

  16. ahmedwaleedmalik commented on Apr 12, 2023

    @ahmedwaleedmalik

    Hey folks, just an update:

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

  17. added a commit that references this issue on Aug 12, 2023
    fc6982c
  18. added a commit that references this issue on Sep 5, 2023
    9b0f8c2
  19. ameukam commented on Dec 9, 2024

    @ameukam
    Member

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

  20. BenTheElder commented on Dec 9, 2024

    @BenTheElder
    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.

  21. ayia-hosni commented on Dec 26, 2025

    @ayia-hosni

    I have updated the remaining registry references in the argoproj/argo-cd installation manifests.

    You can track the progress here:
    argoproj/argo-cd#25802

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    good first issueDenotes an issue ready for a new contributor, according to the "help wanted" guidelines.

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions