-
Hi all,
I can confirm the change is deployed and the host entry is added to /etc/hosts but even though the host dns is enabled, it is not possible to resolve the host name an nslookup from a container. Is this expected behaviour? If so, what's the easiest way to customize the coredns deployment (i.e. change the coredns ConfigMap)? |
Beta Was this translation helpful? Give feedback.
Answered by
smira
Nov 27, 2024
Replies: 1 comment
-
The resolveMemberNames is only supposed to resolve cluster member hostnames, the /etc/hosts is still a host-level hack that doesn't propagate to Kubernetes |
Beta Was this translation helpful? Give feedback.
0 replies
Answer selected by
lholota
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
The resolveMemberNames is only supposed to resolve cluster member hostnames, the /etc/hosts is still a host-level hack that doesn't propagate to Kubernetes