Cluster local domain name should be configurable
mnp opened this issue · 0 comments
mnp commented
In a textbook normal cluster, pods are given the expected local domain stack with local resolver, like svc.cluster.local
.
somepod$ cat /etc/resolv.conf
nameserver 10.76.16.10
search mycorp.svc.cluster.local svc.cluster.local cluster.local us-central1-c.c.mycorp-dev-12345.internal c.mycorp-dev-12345.internal google.internal
options ndots:5
However, if a user wants external DNS, such as VPC-scoped DNS but this is probably not a gke specific problem, all pods will be created with a cluster-themed name stack and an external resolver (the cluster is named mycorp-test
):
somepod$ cat /etc/resolv.conf
nameserver 169.254.169.254
search mycorp.svc.mycorp-test svc.mycorp-test mycorp-test us-central1-c.c.mycorp-dev-12345.internal c.mycorp-dev-12345.internal google.internal
options ndots:5
This is great until you see Kots has some hardcoded dependencies on svc.cluster.local
.
299:2021/08/06 19:11:38 unable to connect to api: failed to connect: dial tcp: lookup kotsadm.mycorp.svc.cluster.local on ***HIDDEN***:53: no such host
300:2021/08/06 19:11:40 connecting to api at http://kotsadm.mycorp.svc.cluster.local:3000
Maybe this should be configurable somewhere?