By leifcr
Currently image-pull-progress-deadline is set to 2m. For larger images or slow pulls from busy registries, this needs to be increased. This results in ImagePullBackOff when the cluster is upgraded and many images are pulled at the same time.
By increasing it to at least 5m, this would solve pulling images when a cluster is upgraded and restarted at the same time.
The issue is when the cluster ends up trying to pull e.g large images simultaneously, all end up timing out.
The issue happens both with Docker registry and Gitlab registry. I tested with images ~2GB, and pulling 5 simultaneously on a droplet takes about 4-5 minutes.
This textbox defaults to using Markdown to format your answer.
You can type !ref in this text area to quickly search our full set of tutorials, documentation & marketplace offerings and insert the link!
That’s a good point! I think that you could submit a bug report via your DO control panel -> go to Kubernetes and on the bottom right there should be a blue horn button that you could click and submit the bug/feature report. That way it would go to the right department.
Become a contributor for community
Get paid to write technical tutorials and select a tech-focused charity to receive a matching donation.
DigitalOcean Documentation
Full documentation for every DigitalOcean product.
Resources for startups and SMBs
The Wave has everything you need to know about building a business, from raising funding to marketing your product.
The developer cloud
Scale up as you grow — whether you're running one virtual machine or ten thousand.
Get started for free
Sign up and get $200 in credit for your first 60 days with DigitalOcean.*
*This promotional offer applies to new accounts only.