Coredns charm does not respect image-registry config if set
Bug #1931154 reported by
Chris Johnston
This bug affects 2 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
CoreDNS Charm |
Won't Fix
|
Undecided
|
Unassigned |
Bug Description
While the CoreDNS charm allows for the image to be passed as a resource, it should also allow for pulling the image from a local registry. As such, it should respect the image-registry config option if defined in the kubernetes-master charm. Requiring the image to be passed as a resource is a different behaviour than the rest of the Kubernetes charms and adds extra complexity to a deployment without free access to the internet.
tags: | added: sts |
Changed in charm-coredns: | |
assignee: | nobody → Tiago Pasqualini da Silva (tiago.pasqualini) |
Changed in charm-coredns: | |
assignee: | Tiago Pasqualini da Silva (tiago.pasqualini) → nobody |
Changed in charm-coredns: | |
milestone: | none → 1.24+ck1 |
status: | New → Triaged |
Changed in charm-coredns: | |
milestone: | 1.24+ck1 → none |
To post a comment you must log in.
With the conversion over to the sidecar charm, the coreDNS image is now provided as an OCI image resource. Status is now Won't Fix