support docker registry in containerd deployments
Bug #1833579 reported by
Kevin W Monroe
This bug affects 2 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Containerd Subordinate Charm |
Fix Released
|
Medium
|
Joseph Borg | ||
Docker Subordinate Charm |
Fix Released
|
Medium
|
Joseph Borg | ||
Kubernetes Control Plane Charm |
Fix Released
|
Medium
|
Joseph Borg | ||
Kubernetes Worker Charm |
Fix Released
|
Medium
|
Joseph Borg |
Bug Description
When docker-registry is related to k8s charms, assumptions are made about what client configuration needs to be done. This includes things like "insecure registry" config in docker's daemon.json or running "docker login" for registries that require auth.
This doesn't make sense in a containerd environment where config and client applications like 'docker' may not even be present.
We should conditionally determine which container runtime is present and take appropriate action when a docker-registry is related to either docker- or containerd-based k8s deployments.
Changed in charm-kubernetes-worker: | |
status: | New → Triaged |
assignee: | nobody → Joseph Borg (joeborg) |
importance: | Undecided → Medium |
Changed in charm-kubernetes-worker: | |
status: | Triaged → In Progress |
Changed in charm-kubernetes-worker: | |
status: | In Progress → Fix Committed |
Changed in charm-containerd: | |
status: | New → Fix Committed |
importance: | Undecided → Medium |
assignee: | nobody → Joseph Borg (joeborg) |
no longer affects: | charm-kubernetes-worker |
Changed in charm-containerd: | |
milestone: | none → 1.15+ck1 |
Changed in charm-docker: | |
assignee: | nobody → Joseph Borg (joeborg) |
Changed in charm-kubernetes-master: | |
assignee: | nobody → Joseph Borg (joeborg) |
Changed in charm-kubernetes-worker: | |
assignee: | nobody → Joseph Borg (joeborg) |
Changed in charm-containerd: | |
status: | Fix Committed → Fix Released |
Changed in charm-docker: | |
status: | Fix Committed → Fix Released |
Changed in charm-kubernetes-master: | |
status: | Fix Committed → Fix Released |
Changed in charm-kubernetes-worker: | |
status: | Fix Committed → Fix Released |
To post a comment you must log in.
Targeting k8s-worker, though I think the fix will actually need to be make in https:/ /github. com/charmed- kubernetes/ layer-kubernete s-master- worker- base/