Changing extra_servers has not effect

Bug #2000145 reported by Diko Parvanov
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
CoreDNS Charm
Incomplete
Undecided
Unassigned

Bug Description

Specifying extra_servers on the charm config has no effect, it is not utilized anywhere in the charm code.

Diko Parvanov (dparv)
summary: - extra_servers is not used anywhere in the code
+ Changing extra_servers has not effect
Revision history for this message
George Kraft (cynerva) wrote :

As I understand it, all of the charm config options are passed in when the corefile template is rendered here: https://github.com/charmed-kubernetes/charm-coredns/blob/5e00f0304cf7f35888d64d263a80a841819924b6/src/charm.py#L151

And the extra_servers option specifically is referenced in the default corefile template here: https://github.com/charmed-kubernetes/charm-coredns/blob/5e00f0304cf7f35888d64d263a80a841819924b6/config.yaml#L38

It looks to me like the extra_servers config *is* utilized in the charm code via the above template render. Am I missing something?

If you encountered an issue with the extra_servers config, please provide more details. What did you do, and what did you see that indicates there's an issue?

Changed in charm-coredns:
status: New → Incomplete
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.