cleanup references to k8s.gcr.io and gcr.io/google-containers

[BenTheElder]

These hosts are deprecated. registry.k8s.io is the current community host.

images can be migrated 1:1 as all old images exist, however if you're still using an image from gcr.io/google-containers it must be really old, like 7+ years, and you should consider finding a recently patched alternative ...

There is at least one reference in:

sig-storage-local-static-provisioner/examples/gke-daemonset-raid-disks.yaml

Line 29 in 695ff8a

image: gcr.io/google-containers/startup-script:v1

/kind bug

[niranjandarshann]

I think startup-script:v1 image is available on registry.k8s.io
We can use that image in place of it. startup-script have two version v1 and v2 .
WDYT!

[niranjandarshann]

If it look good then i would like to work on it

[niranjandarshann]

As i can see that one of the blog has mentioned that gcr is updated to registry.k8s.io https://kubernetes.io/blog/2022/11/28/registry-k8s-io-faster-cheaper-ga/

[BenTheElder]

I think startup-script:v1 image is available on registry.k8s.io
We can use that image in place of it. startup-script have two version v1 and v2 .
WDYT!

You can but this is the same image and it is extremely old and unmaintained, so a replacement should be considered.
However, at least moving to the currently supported host would also be a good start.

[BenTheElder]

Those builds are inherently older than even k8s.gcr.io, they are available on gcr.io/google-containers (the original host for the project, deprecated for far longer, at least since ~2018), so they're going to be riddled with CVEs.