Answer the question
In order to leave comments, you need to log in
Why does coredns stop resolving requests?
Good afternoon!
CoreDNS on kubernetes cluster stops responding and pod logs are empty. However, if you recreate the CoreDNS pods (simply by deleting the old ones), then the problem goes away for a while.
Haven't encountered this?
Kubernetes v1.23.3, CoreDNS-1.8.6.
Busybox examples:
[[email protected] ~]$ kubectl run -i -t busybox --image=busybox:1.28.4 --restart=Never && kubectl delete pod busybox
If you don't see a command prompt , try pressing enter.
/ # ping ya.ru
ping: bad address 'ya.ru'
[[email protected] ~]$ kubectl get pods -n kube-system
NAME READY STATUS RESTARTS AGE
coredns-64897985d-bbktx 1/1 Running 0 19h
coredns-64897985d-dq7w9 1/1 Running 0 16h [alex
@
atm-srv-01 ~]$ kubectl delete pods
$ kubectl run -i -t busybox --image=busybox:1.28.4 --restart=Never && kubectl delete pod busybox
If you don't see a command prompt, try pressing enter.
/ # ping ya.ru
PING ya.ru (87.250.250.242): 56 data bytes
64 bytes from 87.250.250.242: seq=0 ttl=249 time=6.162 ms
64 bytes from 87.250.250.242: seq=1 ttl=249 time =6.843ms
Answer the question
In order to leave comments, you need to log in
Didn't find what you were looking for?
Ask your questionAsk a Question
731 491 924 answers to any question