Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Cluster local domain name should be configurable #2064

Open
mnp opened this issue Aug 9, 2021 · 0 comments
Open

Cluster local domain name should be configurable #2064

mnp opened this issue Aug 9, 2021 · 0 comments

Comments

@mnp
Copy link

mnp commented Aug 9, 2021

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?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant