chore: replace registry for the pause container, fix multicluster test#14918
Merged
chore: replace registry for the pause container, fix multicluster test#14918
pause container, fix multicluster test#14918Conversation
For the past few days, pulling `gcr.io/google_containers/pause:3.2` has failed sporadically: ``` $ docker pull gcr.io/google_containers/pause:3.2 Error response from daemon: unknown: failed to resolve reference "gcr.io/google_containers/pause:3.2": unexpected status from HEAD request to https://gcr.io/v2/google_containers/pause/manifests/3.2: 400 Bad Request ``` Also Artifact Hub scanning is failing: ``` error scanning image gcr.io/google_containers/pause:3.2: error running trivy on image gcr.io/google_containers/pause:3.2: 2026-02-11T18:45:49Z FATAL Fatal error run error: image scan error: scan error: scan failed: failed analysis: unable to get the image ID: unable to get the image ID: GET https://gcr.io/v2/google_containers/pause/blobs/sha256:80d28bedfe5dec59da9ebf8e6260224ac9008ab5c11dbbe16ee3ba3e4439ac2c: NAME_INVALID: Request contains an invalid argument. (package linkerd-multicluster:2025.10.6) ``` It appears the `gcr.io/google_containers` registry is no longer favored and instead the `registry.k8s.io` has been what's [officially supported](https://kubernetes.io/blog/2022/11/28/registry-k8s-io-faster-cheaper-ga/), so we're switching to that one.
adleong
approved these changes
Feb 11, 2026
alpeb
force-pushed
the
alpeb/pause-registry
branch
5 times, most recently
from
60d06fa to
97249bb
Compare
alpeb
force-pushed
the
alpeb/pause-registry
branch
from
97249bb to
be5121b
Compare
adleong
approved these changes
Feb 13, 2026
justfile
Outdated
| # Run the multicluster tests with cluster setup | ||
| mc-test: mc-test-load mc-test-run | ||
| mc-install-gwapi: | ||
| {{ _kubectl }} apply -f https://github.com/kubernetes-sigs/gateway-api/releases/download/v1.2.0/experimental-install.yaml |
Member
There was a problem hiding this comment.
probably want to pull this gwapi version into an argument or env var or something so that it's override able and so that this constant is easier to find and update when we want to increase the gwapi version we want to test with.
alpeb
changed the title
pause containerpause container, fix multicluster test
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
pausecontainer registry changeFor the past few days, pulling
gcr.io/google_containers/pause:3.2has failed sporadically:Also Artifact Hub scanning is failing:
It appears the
gcr.io/google_containersregistry is no longer favored and instead theregistry.k8s.iohas been what's officially supported, so we're switching to that one.Don't install Gateway API in the multicluster integration test target cluster
As of k8s v1.34, k3d's Traefik is installing the Gateway API on its own, among which there is a
backendtglspoliciesCRD pointing to v1.4, which conflicts with v1.2.0 that we are attempting to install.Therefore this change moves the GWAPI installation step from the go test to the actions workflow, applying the GWAPI manifests only where necessary.