Ingress-nginx: Is your container registry down?

Created on 20 May 2020  路  5Comments  路  Source: kubernetes/ingress-nginx

Failed to pull image "quay.io/kubernetes-ingress-controller/nginx-ingress-controller:0.32.0": rpc error: code = Unknown desc = Error response from daemon: Get https://quay.io/v2/kubernetes-ingress-controller/nginx-ingress-controller/manifests/0.32.0: received unexpected HTTP status: 500 Internal Server Error

kinsupport

Most helpful comment

thanks!
running kubectl set image deployment/ingress-nginx-controller controller=gcr.io/k8s-staging-ingress-nginx/nginx-ingress-controller:0.32.0 -n ingress-nginx helped

All 5 comments

Closing. Yes, quay.io is having issues https://status.quay.io/

thanks

same thing today

@wlucjan please check https://github.com/kubernetes/ingress-nginx/issues/5573

Staging copy of the last release
gcr.io/k8s-staging-ingress-nginx/nginx-ingress-controller:0.32.0

thanks!
running kubectl set image deployment/ingress-nginx-controller controller=gcr.io/k8s-staging-ingress-nginx/nginx-ingress-controller:0.32.0 -n ingress-nginx helped

Was this page helpful?
0 / 5 - 0 ratings