In some GKE clusters, there is a bug where hostNetwork: true and dnsPolicy: ClusterFirstWithHostNet results in failed DNS queries.
The solution is to set dnsPolicy: None and provide your own dnsConfig.
This PR adds agent.dnsConfig to the Helm chart values, allowing users to implement this workaround to the GKE issue or specify any other dnsConfig they wish.
In some GKE clusters, there is a bug where
hostNetwork: true
anddnsPolicy: ClusterFirstWithHostNet
results in failed DNS queries.The solution is to set
dnsPolicy: None
and provide your owndnsConfig
.This PR adds
agent.dnsConfig
to the Helm chart values, allowing users to implement this workaround to the GKE issue or specify any otherdnsConfig
they wish.https://cloud.google.com/kubernetes-engine/docs/how-to/nodelocal-dns-cache#dns_timeout