Cloudflare Tunnels is using the wrong DNS server on my k8s cluster
from SpiderUnderUrBed@lemmy.zip to selfhosted@lemmy.world on 02 May 11:37
https://lemmy.zip/post/37670598
from SpiderUnderUrBed@lemmy.zip to selfhosted@lemmy.world on 02 May 11:37
https://lemmy.zip/post/37670598
^ output of my resolv.conf and cloudflare logs
kube-system kube-dns ClusterIP 10.90.0.10 <none> 53/UDP,53/TCP,9153/TCP 2d15h
^ my service ip for kubedns
^ my cloudflare config
How come, despite there being no mention of 8.8.8.8 on my system, in any other dns file for kubedns, not in my resolv.conf, tunnels, is now, incorrectly, trying to use that, to resolve internal ips, it does not make any sense
I think internal DNS resolution is overall working fine, here is a example of me accessing traefik from one of my pods:
spiderunderurbed@raspberrypi:~/k8s $ kubectl exec -it wordpress-7767b5d9c4-qh59n -- curl traefik.default.svc.cluster.local 404 page not found spiderunderurbed@raspberrypi:~/k8s $
^ means traefik was accessed, it is accessed as its my ingress, and there is nothing about 8.8.8.8 in there, might be baked in my CF.
threaded - newest
Seems like you e changed your DNS settings and didn’t update everything after doing that…
You need to update absolutely everything that was every deployed or configured in that cluster after changing something like DNS settings or core network services.
Ok so, I think it was running on the wrong node and using thats resolv.conf which I did not update, but I am getting a new issue:
kube-dns usually isnt supposed to give a i/o timeout when going to external domains, im pretty sure its supposed to forward it to another dns server, or do i have to configure that?
That’s from a disconnected Cloudflare tunnel connection. Are you trying to run Cloudflare Tunnel inside your cluster for some reason?
Nevermind, fixed, this is what I tried applying, or maybe i should have waited for a bit and it might of worked, regardless, just incase its useful to anyone:
The issue is solved now, thanks