contrib/kind: no longer create local docker registry

[squeed]

Now that we use kind load docker-image, it's not necessary to push images to a local registry as well.

[bimmlerd]

cool! small nit about the image names

[bimmlerd]

it's a bit confusing to still have these referring to localhost:5000 without that being an actual registry, can we do something about that?

[squeed]

I was trying to decide what to do; by default, the built images have the tag quay.io/cilium/cilium-dev:local. As long as there's no chance of someone accidentally pushing that image to quay, we could keep it. Otherwise, some sort of unpushable tag would be better.

[squeed]

/test

Job 'Cilium-PR-K8s-1.25-kernel-4.19' failed:

Click to show.

Test Name

K8sDatapathServicesTest Checks E/W loadbalancing (ClusterIP, NodePort from inside cluster, etc) Tests NodePort inside cluster (kube-proxy) with IPSec and externalTrafficPolicy=Local

Failure Output

FAIL: Request from k8s1 to service http://[fd04::11]:32569 failed

If it is a flake and a GitHub issue doesn't already exist to track it, comment /mlh new-flake Cilium-PR-K8s-1.25-kernel-4.19 so I can create one.

[squeed]

I seem to recall some datapath tests relying on the local registry, but I can't actually find it in the codebase. Let's see if the tests pass :-)

[squeed]

Test failures are unrelated; GKE failed to start up (doesn't use kind) and a known flake -- #24648

[squeed]

Manually marking as ready-to-merge, since the only failing tests don't even use kind. Tophat, feel free to disagree.