Skip to content
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

Failed to pull image quay.io/kubernetes-ingress-controller/... #5611

Closed
guyradford opened this issue May 28, 2020 · 7 comments
Closed

Failed to pull image quay.io/kubernetes-ingress-controller/... #5611

guyradford opened this issue May 28, 2020 · 7 comments
Labels
kind/bug Categorizes issue or PR as related to a bug.

Comments

@guyradford
Copy link

Hi,

I know you will be fully aware that quey.io is currently unavailable, this I also assume is a very rare event.

However, they have now been down for 4 hours.
Are there plans to host images via multiple providers?

As far as I can tell Kubernetes does not support backup images locations, I will be raising a suggestion there too.

Thank you
Guy

@guyradford guyradford added the kind/bug Categorizes issue or PR as related to a bug. label May 28, 2020
@robertvanhoesel
Copy link

Since the latest version a mirror is being pushed to GCR #5573

You can pull the latest from:
gcr.io/k8s-staging-ingress-nginx/nginx-ingress-controller:0.32.0

@jemag
Copy link

jemag commented May 28, 2020

given Quay.io terrible track record lately, wouldn't it make more sense to just use the gcr.io registry as the default one instead?

@aledbf
Copy link
Member

aledbf commented May 28, 2020

Closing. As @robertvanhoesel commented, we have a temporal copy of the image in gcr now.

@aledbf aledbf closed this as completed May 28, 2020
@aledbf
Copy link
Member

aledbf commented May 28, 2020

@jemag No. The project has been using quay.io for four and a half years and this is the second important outage.

I have been working since the last quay.io outage to start pushing to gcr.io as a backup.
The plan is to have all the automation needed for this for the next release.
For some context about this work:

@aledbf
Copy link
Member

aledbf commented May 28, 2020

Also, it is important to mention that this can happen to any of the available options.
Never it is a good idea to overreact after an outage.

@jemag
Copy link

jemag commented May 28, 2020

I appreciate the backup image and I do understand that you have a long working relationship with them.

Perhaps it was overreaction on my part, however 3 outage in a single month (2 of them being multiple hours) seemed a bit concerning. This is not something I have witnessed with other providers.

Either way, it is merely a suggestion. Thank you for providing the context about your work

@guyradford
Copy link
Author

I fully agree not to overreact, Using most big providers will give a high 9 count, two an even higher count. There will never be a perfect solution.

Thank you for your answers and keep up the great work.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/bug Categorizes issue or PR as related to a bug.
Projects
None yet
Development

No branches or pull requests

4 participants