Unable to use private docker registry: no managed way to supply CA cert

[Paul Goins]

One of our customers wanted to use a private docker registry for supplying images. There was no need for credentials; the registry was open access. However, the server's certificate was signed by a custom CA.

We probably should have a managed way to allow for using a private registry like this, and a start for that would be simply a way to set the CA cert via Juju.

Workaround: Place the customer's custom CA cert in /etc/ssl/certs/.

(Note: Docker supposedly supports saving CA certs to /etc/docker/certs.d/<hostname>/ca.crt, however I could not get that to work myself.)

[Drew Freiberger (afreiberger)]

This bug addressed adding a private registry:

https://bugs.launchpad.net/charm-kubernetes-master/+bug/1828853

This bug addresses the need for an external CA to be supported by k8s-worker charms:

https://bugs.launchpad.net/charm-kubernetes-worker/+bug/1831153

[Paul Goins (vultaire)]

Thanks Drew; I've referred those 2 tickets instead of this one in the case in question.