This message was deleted.
# k3s
a
This message was deleted.
k
Coincidence that I had the same issue today. Not sure what I did to fix this particular error. It might be that I verified that the coredns pod was running correctly, which is wasn't. It took about 20 seconds to DNS outside the pod. After I deleted the pod it automatically fixed itself, as well as the 20second delay.
l
let me know if you run into it again, im trying to start from scratch now
k
Have you verified that it's the one pod, or are there multiple pods that are failing?
and if you exec to one of your pods, what happens if you type:
openssl s_client <http://google.com|google.com>
l
im setting all up again, will let you know when i do, one question did you manually configure iptables?
k
i haven't configured iptables at all
l
what guide are you following btw if any
k
For what particular aspect?
l
like what kind of project are you doing atm
k
For that I'm not really following any tutorial. I for example want to deploy a .NET 6 WebApi and VS scaffolds a dockerfile for me. I just have to do all other things
l
gotcha
k
But I do know that there's DNS issues within k3s, or rather.. sometimes those infra pods seem to be a bit unstable. So it might be worth to check whether or not your coredns pod is running normally for example. I did use this guide to test my DNS resolvement issues for example; https://kubernetes.io/docs/tasks/administer-cluster/dns-debugging-resolution/
Not that it magically started working, but it did show me that the coredns pod wasn't running (bugged out). Through Rancher UI i deleted the pod so it would recreate itself, and suddenly everything started working 20 times better.
@limited-traffic-81887 Did you figure it out?