vagrant-kubeadm-kubernetes icon indicating copy to clipboard operation
vagrant-kubeadm-kubernetes copied to clipboard

Published 20 hours ago • verified publisher icon techiescamp

The DNS for services is not working after the fresh installation

Open yxiao168 opened this issue 6 months ago • 0 comments

After the set up of the cluster for the 1st time, the DNS for services usually doesn't work. Only after the deletion of the coredns-* pods as below (to force coredns to restart) , the DNS for services starts to work.

$ k -n kube-system delete pod coredns-6f6b679f8f-4mvnz pod "coredns-6f6b679f8f-4mvnz" deleted $ k -n kube-system delete pod coredns-6f6b679f8f-ggqcs pod "coredns-6f6b679f8f-ggqcs" deleted

This bug exists with all Kubernetes versions. It seems that the setup script should be twisted to cop with this situation.

I used "nslookup", "curl", "nc" from the image "curlimages/curl" in my tests.

yxiao168 avatar Aug 21 '24 02:08 yxiao168