Skip to content

The DNS for services is not working after the fresh installation #74

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
yxiao168 opened this issue Aug 21, 2024 · 0 comments
Open

The DNS for services is not working after the fresh installation #74

yxiao168 opened this issue Aug 21, 2024 · 0 comments

Comments

@yxiao168
Copy link

yxiao168 commented Aug 21, 2024

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant