Report this

What is the reason for this report?

Gitlab CI/CD deployment upgrade in managed Kube fails with ImagePullBackOff

Posted on December 16, 2019

Hi. I’m running managed Kube with the latest version. When I do a CI/CD deployment from Gitlab, everything is green on Gitlab’s side, the deployment fires, but it will never successfully roll out in Kube. It stays stuck with an ImagePullBackOff error, unauthorized: HTTP Basic: Access denied. On the Kube side, one pod is upgraded, a fourth pod is created that displays this error, and the other two pods remain untouched.

If I manually delete the deployment before running the Gitlab pipeline, everything works. I’m at a loss for where I’m going wrong. I upgraded to more memory just to ensure it wasn’t a memory issue (I’m running basic nodes), but the problem persisted.



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!

The developer cloud

Scale up as you grow — whether you're running one virtual machine or ten thousand.

Start building today

From GPU-powered inference and Kubernetes to managed databases and storage, get everything you need to build, scale, and deploy intelligent applications.

Dark mode is coming soon.