Hello! I have an "at-home" cluster setup on 3 rasperry pis, the master and 2 nodes are both healthy and "ready". And I have a healthy running pod printing something every 2 seconds on a loop. the issue is that, from either the master, or my desktop kubectl, I am getting a proxy 503 error when running

kubectl logs hello-raspi

the full error looks like this

Error from server: Get "<https://10.0.0.142:10250/containerLogs/default/hello-raspi/hello-raspi>": proxy error from 127.0.0.1:6443 while dialing 10.0.0.142:10250, code 503: 503 Service Unavailable

. Can anyone point me in the right direction, google is tough on a specific error like this

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.

let me know if you run into it again, im trying to start from scratch now

Have you verified that it's the one pod, or are there multiple pods that are failing?

im setting all up again, will let you know when i do, one question did you manually configure iptables?

i haven't configured iptables at all

what guide are you following btw if any

For what particular aspect?

like what kind of project are you doing atm

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

gotcha

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/