-
Notifications
You must be signed in to change notification settings - Fork 65
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
error pulling image on GKE in Singapore #116
Comments
On another, all-default cluster in
|
From a workstation on the US west-coast I can pull the backing image for this region:
|
In
|
@ameukam found this is because asia-southeast1 has a cloud run region pointing at the matching AR region, but we have no AR instance there. We need to audit that all the cloud run regions do have matching AR, we missed this one at least flipping from GCR to AR. |
kubernetes/k8s.io#4337 is where we moved to AR |
Confirmed @ameukam has rolled out a fix for this:
|
kubernetes/k8s.io#4337 I've audited all of the regions, AFAICT this was the only affected region. |
Related to: kubernetes/registry.k8s.io#116 The Cloud Run service in this region pointing at the matching AR region, but we have no AR instance there. Signed-off-by: Arnaud Meukam <ameukam@gmail.com>
Thank you @BenTheElder. Everything is working now |
Thanks for the report and for confirming! |
fix was merged in kubernetes/k8s.io#4352 |
Following #115 (comment) (which seems unrelated to the original issue, which was seemingly an issue with the loadbalancer when removing europe-west3), I couldn't reproduce locally, but I can reproduce the issue on a standard GKE cluster in
asia-southeast1-a
kubectl run --image=registry.k8s.io/ingress-nginx/kube-webhook-certgen:v1.3.0@sha256:549e71a6ca248c5abd51cdb73dbc3083df62cf92ed5e6147c780e30f7e007a47 test
kubectl describe pod test
observe events:
cc @winggundamth
/assign
/priority critical-urgent
The text was updated successfully, but these errors were encountered: