ImagePullBackOff

Kubernetes
#1

I am facing an ImagePullBackOff issue in a Kubernetes pod due to an expired TLS certificate for a private Docker registry (running in a container). After renewing the certificate, a new error appeared because the Common Name (CN) is no longer sufficient for validation, as modern TLS requires Subject Alternative Names (SANs). I tried to manually pull the image used by the pod, but it failed. However, after updating /etc/docker/daemon.json with:

{
“insecure-registries”: [“dock-reg-dev.kola.ma:443”]
}
I was able to pull the image manually using docker pull, but the ImagePullBackOff issue still persists in the Kubernetes pod

#2

I expect that this particular docker registry will have a web site and an issue queue that would explain how to upgrade things like this. You’re probably best off posing the question there, I think.

#3

The registry is in my container, as I mentioned above, I resolved the issue.
Thank you for your reply