Open mrbobbytables opened 1 year ago
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
👍
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 kubevirt
, meshery
and thanosbench
.
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 https://github.com/helm/helm/pull/11829
can you make that a check?
cc @mrbobbytables @jeefy
Hello fro the
Helm
most of the changes are in thehelm/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 👍
I'm currently looking at OpenEBS
, VS Code Kubernetes Tools
, WasmEdge Runtime
, k8gb
, knative
.
I am looking at k3s
kudo
and keptn
and telepresence
I am looking at cert-manager
, flux
, kyverno
, longhorn
and OpenKruise
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!
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.
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.
Thank you for calling that out. I just opened up a PR to fix that.
Hey all, I'll be taking up Confidential Containers
, Cloud Development Kit for Kubernetes (cdk8s)
, Crossplane
, Falco
, and Konveyor
.
Taking it up for dapr
.
No changes needed for metal3-io. One is sample output in a blog post, the others in an archived repo.
For Argo an issue has already been opened: https://github.com/argoproj/argo-cd/pull/12362/commits
Hi folks, I looked into the following orgs:
Will take a look at other affected spaces tomorrow as well.
k8s.gcr.io/pause:3.5
with a custom image for containerd v1.5.3. I'm working for Aeraki Mesh
, Akri
I'm working for
Aeraki Mesh
,Akri
@NitishKumar06 I don't think we need anything for Aeraki Mesh
.
Aaeraki-mesh: N/A; only an old fork https://github.com/aeraki-mesh/istio is affected that was last updated on Sep 23, 2021.
I can work on the following:
@ArkaSaha30 some of these orgs have already been covered. Please check the comments. The PR description is regularly updated based on these comments but the description can lag behind a bit.
Hello folks, here is the list of PRs that I've made to the following orgs:
I'll take up Krustlet
, Nocalhost
, OpenELB
, ORAS
I'm working on kubewarden
Hello @ahmedwaleedmalik, as per your suggestion
External Secrets Operator: These are packaged operators for OperatorHub. I'm not a fan of updating the hosted manifests directly unless the owners of those operators roll out a new release and add a new version in the repos.
Should we skip it for now? OR do we need to make further communications before we take an action?
Hello @ahmedwaleedmalik, as per your suggestion
External Secrets Operator: These are packaged operators for OperatorHub. I'm not a fan of updating the hosted manifests directly unless the owners of those operators roll out a new release and add a new version in the repos.
Should we skip it for now? OR do we need to make further communications before we take an action?
I would recommend that we skip it. cc @mrbobbytables
There seems to be no required changes for ORAS
organization. The only repository that has k8s.gcr.io
has been archived and is read-only.
@mrbobbytables OpenELB
is incorrectly linked to https://github.com/kubesphere
There should be a separate entry for Kubesphere
with search query link: https://github.com/search?q=org%3Akubesphere%20%22k8s.gcr.io%22&type=code
OpenELB link: https://github.com/openelb
OpenELBsearch query link: https://github.com/search?q=org%3AOpenELB+%22k8s.gcr.io%22&type=code
@mrbobbytables
OpenELB
is incorrectly linked to https://github.com/kubesphere There should be a separate entry forKubesphere
with search query link: https://github.com/search?q=org%3Akubesphere%20%22k8s.gcr.io%22&type=code OpenELB link: https://github.com/openelb OpenELBsearch query link: https://github.com/search?q=org%3AOpenELB+%22k8s.gcr.io%22&type=code
Thanks - I got the location from the CNCF project list: https://github.com/cncf/toc/blob/main/docs/PROJECTS.csv
Would probably be worth updating that to point to the right location for OpenELB
Hey folks, just an update:
Had to take over a few subtasks(organizations) since they were stalled for quite some time.
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