I have deployed charmed kubernetes with the docker-registry charm, and I could build and push an image to the registry. However, if I want to pull that image in a kubernetes deployment, I get error:
Warning Failed 6s (x2 over 21s) kubelet, juju-59fee34-k8s-paul-8 Failed to pull image “registry_ip:registry_port/frontend:latest”: rpc error: code = Unknown desc = failed to pull and unpack image “registry_ip:registry_port/frontend:latest”: failed to resolve reference “registry_ip:registry_port/frontend:latest”: failed to do request: Head https://registry_ip:registry_port/v2/frontend/manifests/latest: remote error: tls: bad certificate
Aren’t easyrsa or vault supposed to manage certificates through the added relations ? What I have noticed is that a juju-docker-registry.pem has been installed on the clients, but that does obviously not solve the problem.
I am running into the exact same problem. Recently installed charmed kubernetes with private docker registry.
=====
Warning Failed 9s (x2 over 22s) kubelet, juju-e53148-1 Failed to pull image "ip:port/image-name": rpc error: code = Unknown desc = failed to pull and unpack image "ip:port/image-name": failed to resolve reference "ip:port/image-name": failed to do request: Head https://ip:port/image-name: remote error: tls: bad certificate