Switch to registry.k8s.io

[ameukam]

Reference issue:

• [Action Required] Update references from k8s.gcr.io to registry.k8s.io #2231

Part of:

• [Umbrella Issue] Migrate K8s projects from k8s.gcr.io -> registry.k8s.io k8s.io#4738

Signed-off-by: Arnaud Meukam ameukam@gmail.com

[mborsz]

/hold

We have had some problems with using registry.k8s.io in testing environments without public internet access.
We need to test this change in such environment before merging or adapt the tests running there to have access to registry.k8s.io.

[ameukam]

testing environments without public internet access.

which environments are we talking about ? related to the Kubernetes project ?

[mborsz]

The last time this change has broken GKE internal tests (#2044) which are using private nodes without internet access. I'm not sure what is a state now and if we expect to registry.k8s.io to work in such cases. I asked the current oncall to investigate this issue.

[aojea]

The last time this change has broken GKE internal tests (#2044) which are using private nodes without internet access. I'm not sure what is a state now and if we expect to registry.k8s.io to work in such cases. I asked the current oncall to investigate this issue.

cc: @BenTheElder

[BenTheElder]

So from an OSS perspective, GKE internal test environment issues should really not be blocking upstream changes unless they're surfacing a bug ...

Kubernetes has a merged KEP to cease allowing any new images in GCR for 1.27+, and SIG K8s Infra could choose to shut down GCR even sooner as all images are available at registry.k8s.io and Kubernetes is massively over-budget (think $4M spend rate on $3M GCP budget), primarily due to content download costs.

Kubernetes has been on registry.k8s.io since 1.25, released August '22.

I see the internal bug and will follow-up on GKE's options there.

[Argh4k]

Hi, we updated gke internal tests and we are ready to go with this change.

[ameukam]

@mborsz @marseel @wojtek-t PTAL.

[marseel]

/approve
but waiting for someone from GKE team to unhold when they are ready to merge.

[aojea]

as a followup we should update the pause image version, right now kubernetes uses the 3.9 version and this repo seems to be useing 3.1 , I don't know if that can be an issue though

[BenTheElder]

/lgtm
yeah, pause can be a separate PR, I doubt this repo depends on the newer features of pause and it's orthogonal

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: ameukam, BenTheElder, marseel

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

• clusterloader2/OWNERS [marseel]
• dns/OWNERS [marseel]
• slo-monitor/OWNERS [marseel]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[Argh4k]

/unhold

[vaibhav2107]

Fixes: #2231