External Docker Registry with Self-Signed CA TLS endpoints not supported by charm
Bug #1831153 reported by
Drew Freiberger
This bug affects 2 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Container Runtime Common Layer |
Fix Released
|
High
|
Kevin W Monroe | ||
Kubernetes Worker Charm |
Invalid
|
Wishlist
|
Unassigned |
Bug Description
When trying to deploy workloads within a kubernetes cluster that point to an external https:/
This is a feature request to allow for adding a mechanism to import a docker-
Changed in charm-kubernetes-worker: | |
importance: | Undecided → Wishlist |
status: | New → Triaged |
Changed in layer-container-runtime-common: | |
status: | Triaged → In Progress |
assignee: | nobody → Kevin W Monroe (kwmonroe) |
Changed in layer-container-runtime-common: | |
milestone: | 1.17 → none |
Changed in layer-container-runtime-common: | |
importance: | Medium → Critical |
tags: | added: review-needed |
Changed in layer-container-runtime-common: | |
milestone: | none → 1.18+ck1 |
Changed in layer-container-runtime-common: | |
status: | In Progress → Fix Committed |
tags: | removed: review-needed |
Changed in layer-container-runtime-common: | |
importance: | Critical → High |
Changed in layer-container-runtime-common: | |
status: | Fix Committed → Fix Released |
To post a comment you must log in.
Manual workaround is to land the CA file(s) into /etc/docker/certs.d directory on each kubernetes-worker node.