start using images from registry.k8s.io

[upodroid]

What type of PR is this?

/kind bug

What this PR does / why we need it:

All end-user facing images need to be served from registry.k8s.io, you can't serve any images hosted at gcr.io/k8-staging-* or us-central1-docker.pkg.dev/k8s-staging-images/* to end users. The project has a policy for serving docker images to end users here.

Unfortunately, we got hit with a large bill, and we need to shut down gcr.io/k8s-staging-gateway-api as soon as possible. To do that:

• I'll promote the missing images for echo-advanced and echo-simple
• Merge switch to using AR staging registry for gateway api kubernetes/k8s.io#9294
• Merge migrate gateway-api to AR staging registry kubernetes/test-infra#36762
• Then merge this PR

Which issue(s) this PR fixes:

Fixes #

Does this PR introduce a user-facing change?:

NONE

[rikatz]

Those are the versions that we have:

https://github.com/kubernetes/k8s.io/blob/main/registry.k8s.io/images/k8s-staging-gateway-api/images.yaml#L18-L21

[upodroid]

Before I backfill the images, I asked this question on Slack

whats the difference between echo-basic and echo-advanced? Also, echo-advanced is a copy of the istio app image which hasn't been updated in a long time

https://kubernetes.slack.com/archives/CR0H13KGA/p1775222564804039?thread_ts=1775079862.624539&cid=CR0H13KGA

[youngnick]

echo-basic is for the north-south tests, while echo-advanced is for east-west mesh cases. You're correct that's it's a copy of the istio app image, the reason to do that was to move the the test artifact under Gateway API's control, rather than being under Istio's control. That way, the Gateway API conformance tests are not dependent on another organization's binary.

[snorwin]

I'm wondering why the whitespace changes weren't caught by the linter. Could you fix them anyway?

[upodroid]

It's supposed to be indented by 2 spaces.

[snorwin]

Yes you are right, it seems we mixed things up, in the conformance tests we do indent with two spaces, but in the examples we don't. Maybe we should harmonize this at some point, but I'm fine with it for now.

[upodroid]

This is ready to be merged, all the images have been promoted to registry.k8s.io, including 1.4 and 1.5

[snorwin]

Thanks @upodroid.

/lgtm

[youngnick]

/approve

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: snorwin, upodroid, youngnick

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

The pull request process is described here

Details

Needs approval from an approver in each of these files:

• OWNERS [youngnick]

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

[upodroid]

We also need to merge this test-infra PR.

kubernetes/test-infra#36762