You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
The text was updated successfully, but these errors were encountered:
Uh oh!
There was an error while loading. Please reload this page.
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.
The text was updated successfully, but these errors were encountered: