core dns load balancer does not get the correct targetPort

[raffaelespazzoli]

the loadbalancer service deployed by setting the option:

exposeCoreDNS: true

is configured with the target port statically set to 53.
In some systems this requires privileges permissions, so user will change this to a different port via the following config:

coredns:
  servers:
    - zone: .
    port: 5353

the load balancer service template be changed to pick this setting.

[k0da]

@raffaelespazzoli atm we maintain CoreDNS service ourselves so coredns chart service settings have no effect

[raffaelespazzoli]

@k0da that is exactly my point. I'm asking to make some changes to the chart to guarantee consistency.

[k0da]

@raffaelespazzoli I think k8gb currently doesn't support running CoreDNS on non standard port. Unfortunately coredns doesn't support setting containerPorts separately. So we can't really support configuration you mentioned.

[raffaelespazzoli]

as of now this prevents deploying k8gb on OpenShift. Maybe we should ask coredns to support this feature in their chart?

[k0da]

Sure, once CoreDNS supports it we can adapt