arrstack: repoint arrproxy oauth2-proxy image off ghcr (fix ImagePullBackOff) #379
Reference in New Issue
Block a user
Delete Branch "benvin/oauth2-proxy-image-fix"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Why
The arrproxy front door is down: the
arrproxy-oauth2sidecar (namespacearrstack) is inImagePullBackOffpullingartifactapi.k8s.syd1.au.unkin.net/ghcr/oauth2-proxy/oauth2-proxy:v7.15.3(401).Root cause:
ghcr.io/oauth2-proxy/oauth2-proxydoes not allow anonymous pulls — its ghcr token endpoint returns{"errors":[{"code":"DENIED"}]}for scoperepository:oauth2-proxy/oauth2-proxy:pull. artifactapi's ghcr remote authenticates anonymously, so it can never obtain a token for this repo and returnsupstream returned 401. Other ghcr images (e.g.valkey-io/valkey-operator) work because ghcr issues them anon tokens.Change
oauth2-proxysidecar image from theghcr/remote todocker-internal/oauth2-proxy:v7.15.3.The image was mirrored into the
docker-internallocal registry fromquay.io/oauth2-proxy/oauth2-proxy:v7.15.3(oauth2-proxy's canonical anon-friendly registry). Full multi-arch manifest list copied; identical digestsha256:10a1165743a192e1940b4708fb9647027185ce11a681a1c5519b442ff7f1f561. The docker-internal path now returns a 200 manifest and is pullable.Follow-up (reproducibility)
The mirror was a one-off
skopeo copy. To make it GitOps-reproducible, a follow-up can add^oauth2-proxy/to the quay remote patterns interraform-artifactapi(config/remote_docker/quay.yaml) and repoint toquay/oauth2-proxy/oauth2-proxy:v7.15.3.4256b09c9bto5a23146513