can't pull cnx-node image on master units when using docker-registry charm with TLS enabled

Bug #1813343 reported by Tim Van Steenburgh
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Tigera Secure EE Charm
Fix Released
Undecided
George Kraft

Bug Description

Opened by Cynerva on 2019-01-22 15:02:49+00:00 at https://github.com/juju-solutions/layer-tigera-secure-ee/issues/6

------------------------------------------------------------

After following the guide here: https://www.ubuntu.com/kubernetes/docs/docker-registry
I configured tigera-secure-ee to use the registry:
juju config tigera-secure-ee registry=<REGISTRY_IP>

On kubernetes-master units, the calico-node service did not come up, as they were unable to pull the image. The kubernetes-worker units came up fine.
I believe the kubernetes-master units need to do what the worker is doing here: configure docker with a CA cert and client certs.

Changed in charm-tigera-secure-ee:
assignee: nobody → George Kraft (cynerva)
status: New → In Progress
Revision history for this message
George Kraft (cynerva) wrote :
Revision history for this message
George Kraft (cynerva) wrote :
George Kraft (cynerva)
Changed in charm-tigera-secure-ee:
status: In Progress → Fix Committed
Changed in charm-tigera-secure-ee:
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.