can't pull cnx-node image on master units when using docker-registry charm with TLS enabled
Bug #1813343 reported by
Tim Van Steenburgh
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:/
-------
After following the guide here: https:/
I configured tigera-secure-ee to use the registry:
juju config tigera-secure-ee registry=
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 |
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.
Pull requests open:
https:/ /github. com/juju- solutions/ kubernetes/ pull/210
https:/ /github. com/juju- solutions/ layer-tigera- secure- ee/pull/ 7
https:/ /github. com/juju- solutions/ layer-calico/ pull/31
https:/ /github. com/juju- solutions/ layer-canal/ pull/30