Reputation: 912
My k3s cluster stopped resolving DNS name for service ClusterIP. I wonder if there is a fix?
Here is an example demonstrating the problem: the actual IP for my ClusterIP service is 10.43.153.152. When I run nslookup, I get the correct name. However, when I run ping for this name, I get a different IP address which is incorrect
/srv $ nslookup 10.43.153.152
Server: 10.43.0.10
Address: 10.43.0.10:53
152.153.43.10.in-addr.arpa name = web-ui.smart-progress-or.svc.cluster.local
/srv $ ping web-ui.smart-progress-or.svc.cluster.local
PING web-ui.smart-progress-or.svc.cluster.local (91.195.240.12): 56 data bytes
64 bytes from 91.195.240.12: seq=0 ttl=42 time=37.107 ms
^C
--- web-ui.smart-progress-or.svc.cluster.local ping statistics ---
1 packets transmitted, 1 packets received, 0% packet loss
round-trip min/avg/max = 37.107/37.107/37.107 ms
nslookup 10.43.153.152 -> web-ui.smart-progress-or.svc.cluster.local
ping web-ui.smart-progress-or.svc.cluster.local -> 91.195.240.12
???
Running on Orange PI, Debian GNU/Linux 12 (bookworm)
Upvotes: 0
Views: 31