simple method for configuring a private container registry
Bug #1828853 reported by
Kevin W Monroe
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Kubernetes Control Plane Charm |
Fix Released
|
Wishlist
|
Kevin W Monroe |
Bug Description
We currently provide support for configuring an 'addons-registry', which allows users to specify a private registry for images used by cdk-addons (eg: coredns, heapster, calico, etc). K8s workers use non-addons images (eg: pause, defaultbackend, etc) and have no easy way to specify that those should also come from a private registry.
We should provide a more generic 'images-registry' config option that will be honored by all K8s charms so that users can specify a private registry in one place and have all images in a K8s deployment come from that.
Changed in charm-kubernetes-master: | |
importance: | Undecided → Wishlist |
status: | New → Triaged |
Changed in charm-kubernetes-master: | |
assignee: | nobody → Kevin W Monroe (kwmonroe) |
Changed in charm-kubernetes-master: | |
status: | Triaged → Fix Committed |
Changed in charm-kubernetes-master: | |
milestone: | none → 1.15 |
Changed in charm-kubernetes-master: | |
status: | Fix Committed → Fix Released |
To post a comment you must log in.
Master work: /github. com/charmed- kubernetes/ charm-kubernete s-master/ pull/24
https:/
Worker work: /github. com/charmed- kubernetes/ charm-kubernete s-worker/ pull/18
https:/