support docker registry in containerd deployments

Bug #1833579 reported by Kevin W Monroe
12
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.

Revision history for this message
Kevin W Monroe (kwmonroe) wrote :

Targeting k8s-worker, though I think the fix will actually need to be make in https://github.com/charmed-kubernetes/layer-kubernetes-master-worker-base/

affects: layer-docker-registry → charm-kubernetes-worker
Changed in charm-kubernetes-worker:
status: New → Triaged
assignee: nobody → Joseph Borg (joeborg)
importance: Undecided → Medium
Joseph Borg (joeborg)
Changed in charm-kubernetes-worker:
status: Triaged → In Progress
Revision history for this message
Joseph Borg (joeborg) wrote :
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
Revision history for this message
George Kraft (cynerva) wrote :
Changed in charm-docker:
status: New → Fix Committed
Changed in charm-kubernetes-master:
status: New → Fix Committed
Changed in charm-kubernetes-worker:
status: New → Fix Committed
Changed in charm-docker:
importance: Undecided → Medium
Changed in charm-kubernetes-master:
importance: Undecided → Medium
Changed in charm-kubernetes-worker:
importance: Undecided → Medium
Revision history for this message
George Kraft (cynerva) wrote :

I'm going to recommend that we do not release this as part of 1.15+ck1. The fixes involve removing the docker-registry relations from kubernetes-master and kubernetes-worker, and adding them to the docker and containerd subordinate charms instead. I don't think it makes sense for us to ship something that changes the relations like this as part of a bug fix release unless there is a strong need for it.

George Kraft (cynerva)
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)
Revision history for this message
Tim Van Steenburgh (tvansteenburgh) wrote :

+1 George, will move to 1.16, thanks for looking.

Changed in charm-docker:
milestone: none → 1.16
Changed in charm-kubernetes-master:
milestone: none → 1.16
Changed in charm-kubernetes-worker:
milestone: none → 1.16
Changed in charm-containerd:
milestone: 1.15+ck1 → 1.16
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.
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.