You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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):
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?
The text was updated successfully, but these errors were encountered:
In a textbook normal cluster, pods are given the expected local domain stack with local resolver, like
svc.cluster.local
.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
):This is great until you see Kots has some hardcoded dependencies on
svc.cluster.local
.Maybe this should be configurable somewhere?
The text was updated successfully, but these errors were encountered: