[wishlist] Config item for a private registry with credentials

Bug #1844079 reported by Xav Paice
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Kubernetes Worker Charm
Invalid
Medium
Joseph Borg

Bug Description

Currently, there's a relation available for the docker-registry charm should we wish to use a private registry. However, we have a case where there's already a private registry outside the environment, and it needs credentials. We currently have no way to inject that information to the Kubernetes workers, and so the registry cannot be used.

Sort of related: https://bugs.launchpad.net/charm-kubernetes-worker/+bug/1831153

Revision history for this message
Tim Van Steenburgh (tvansteenburgh) wrote :

Pretty sure this is possible, but we need to make sure it's documented. Docs need to cover the following scenarios:

- pre 1.15 configuration with docker
- post 1.15 configuration with docker
- post 1.15 configuration with containerd

Changed in charm-kubernetes-worker:
assignee: nobody → Joseph Borg (joeborg)
status: New → Triaged
importance: Undecided → Medium
Revision history for this message
Chris Johnston (cjohnston) wrote :

I believe this is possible now in containerd and Docker.

Revision history for this message
George Kraft (cynerva) wrote :

Yep, thanks for pointing it out. This is possible with the custom_registries config for containerd[1] and the docker-logins config for docker[2].

[1]: https://ubuntu.com/kubernetes/docs/1.19/charm-containerd#custom_registries-description
[2]: https://ubuntu.com/kubernetes/docs/1.19/charm-docker#docker-logins-description

Changed in charm-kubernetes-worker:
status: Triaged → Invalid
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.