Charts: coredns doesn't deploy if loadbalancer is metallb

Created on 29 Apr 2019  路  4Comments  路  Source: helm/charts

BUG REPORT

Version of Helm and Kubernetes:
k8s: 1.14.1
helm: 2.13,1

Which chart:
stable/coredns

What happened:
try to deploy but failed with:

is invalid: spec.ports: Invalid value: []core.ServicePort{core.ServicePort{Name:"udp-53", Protocol:"UDP", Port:53, TargetPort:intstr.IntOrString{Type:0, IntVal:53, StrVal:""}, NodePort:0}, core.ServicePort{Name:"tcp-53", Protocol:"TCP", Port:53, TargetPort:intstr.IntOrString{Type:0, IntVal:53, StrVal:""}, NodePort:0}}: cannot create an external load balancer with mix protocols

How to reproduce it (as minimally and precisely as possible):
install coredns with value override of

serviceType: "LoadBalancer"
loadBalancerIP: "assignable ip"

Anything else we need to know:
k8s doesn't like service port on both tcp and udp for loadbalancer type services: https://metallb.universe.tf/usage/#ip-address-sharing

To resolve I believe 2 services need to be made one for udp and one for tcp
or wait til
https://github.com/kubernetes/kubernetes/issues/23880
is resolved

lifecyclstale

Most helpful comment

workaround which work for me:

      servers:
        - zones:
            - zone: .
              scheme: dns://
              use_tcp: false

All 4 comments

workaround which work for me:

      servers:
        - zones:
            - zone: .
              scheme: dns://
              use_tcp: false

@dano0b's workaround worked for me as well. Thanks mate.

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Any further update will cause the issue/pull request to no longer be considered stale. Thank you for your contributions.

This issue is being automatically closed due to inactivity.

Was this page helpful?
0 / 5 - 0 ratings