Each vCluster has its own DNS service (CoreDNS by default) which allows pods in the vCluster to get the IP addresses of services that are also running in the vCluster. The vCluster syncer ensures that the intuitive naming logic of Kubernetes DNS names for services applies and users can connect to these DNS names which in fact map to the IP address of the synchronized services that are present in the underlying host cluster.
However, this also means that you cannot directly access host services inside the virtual cluster via DNS as well as host pods can only access virtual cluster services by their synced name. vCluster offers a feature to map services from the virtual cluster to the host cluster and vice versa.
Fallback to Host DNS
If fallbackHostDNS is enabled, the vCluster will fallback to the host cluster's DNS for resolving domains. This is useful if the host cluster is using Istio or Dapr and the sidecar containers cannot connect to the central instance. It is also useful if you want to access the host cluster services from within the vCluster. We can enable this feature with: