Support for basic auth

[Tim Van Steenburgh]

The charm currently supports only authentication with a token server.
A common implementation uses native basic authentication with htpasswd: https://docs.docker.com/registry/deploying/#native-basic-auth
The authentication info could then be passed to kubernetes-worker through the relation.

[Tim Van Steenburgh (tvansteenburgh)]

From mthaddon:

"We definitely want this to be done via a juju relation. We should be able to relate a registry to the kubernetes-worker charm and have authentication handled via that."

[Kevin W Monroe (kwmonroe)]

I'm working on the k8s side of this right now, but I just finished a WIP wiki that walks you through using basic auth and tls with a k8s registry:

https://github.com/juju-solutions/bundle-canonical-kubernetes/wiki/WIP:-Private-Docker-Registry

There's more that will tuck under the magic of "juju relate k8s-worker docker-registry", but if anyone wanted to try an authenticated registry today, that'd be the place to start.

[Kevin W Monroe (kwmonroe)]

Basic auth is now supported in the stable docker-registry charm:

https://jujucharms.com/u/containers/docker-registry

And can be configured as described in the readme:

https://github.com/CanonicalLtd/docker-registry-charm#authentication

With kubernetes-worker revision 385 or greater, a relation can be made between the registry and k8s-worker which will enable the worker to login to the registry with the configured basic auth.

[Kevin W Monroe (kwmonroe)]

This has made its way into the latest stable docker-registry and k8s charms.