[BUG] kruise-daemon should use ClusterFirstWithHostNet for the DNS Policy #1447
Labels
kind/good-first-issue
Good for newcomers
kind/good-idea
Good Idea
wontfix
This will not be worked on
Milestone
What happened: kruise-daemon isn't able to resolve internal DNS entries, i.e. a locally host docker proxy
What you expected to happen: kruise-daemon should be able to resolve service.namespace.svc.cluster.local entries
How to reproduce it (as minimally and precisely as possible): host a docker proxy in a cluster and use an ImagePull job to try to pull images through it, DNS lookup will fail
Anything else we need to know?: This is caused by not defining a dnsPolicy and the default ClusterFirst getting assigned, but since it's created with
hostNetwork: true
this has the effect of setting DNS to the node's DNS. It has to be changed manually to use the Cluster DNS, more info at https://kubernetes.io/docs/concepts/services-networking/dns-pod-service/#pod-s-dns-policyEnvironment:
kubectl version
): 1.23.17+k3s1The text was updated successfully, but these errors were encountered: