Skip to content
Discussion options

You must be logged in to vote

I guess you would need to look into your DNS and Kubernetes cluster. They are responsible for DNS resolution. I have no idea what environment do you use, but this can be also sometimes faulty juts on one worker node and when you start a pod on another node it works fine. You can also try to delete the pod and have it recreated in case it was just some temporary glitch.

Replies: 2 comments 2 replies

Comment options

You must be logged in to vote
0 replies
Comment options

You must be logged in to vote
2 replies
@scholzj
Comment options

Answer selected by mausch
@mausch
Comment options

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Category
Q&A
Labels
None yet
3 participants