OAuth2-Proxy Version

Version: v7.15.1

Provider

None

Expected Behaviour

docker pull quay.io/oauth2-proxy/oauth2-proxy:v7.15.1 succeeds and Kubernetes nodes can pull the image.

Current Behaviour

Current Behaviour:
Pulling the image from quay.io fails intermittently with HTTP 502 Bad Gateway errors on blob fetches:
failed to copy: httpReadSeeker: failed open: unexpected status code
https://quay.io/v2/oauth2-proxy/oauth2-proxy/blobs/sha256:c172f...: 502 Bad Gateway
Kubernetes pods go into ImagePullBackOff.

Steps To Reproduce

Steps To Reproduce:

1. Attempt to pull quay.io/oauth2-proxy/oauth2-proxy:v7.15.1 from a Kubernetes cluster
2. Observe 502 errors from quay.io blob endpoints

Possible Solutions

Possible Solutions:
Consider publishing images to a secondary registry (e.g. GitHub Container Registry ghcr.io) as a fallback, or documenting a recommended mirror strategy.

Configuration details or additional information

No response