I'm working with a four-node Raspberry Pi cluster using Kubernetes 1.33 and I've installed Flannel, MetalLB, and the Kubernetes dashboard. I've successfully assigned an external IP to the 'kd-service', but I'm unable to access the dashboard UI from my local network. I've searched online but haven't found any solutions. Any advice would be greatly appreciated! Here are some details from my setup:
- Services:
- kubernetes-dashboard has an external IP: 10.1.40.31
- Pods are showing normal status with the exception of the kubernetes-dashboard-kong-proxy, which is in CrashLoopBackOff.
- I'm using CRI-O to avoid Docker or Containerd.
- I've ensured my MetalLB configuration is correct. I'm just at a loss here.
3 Answers
Looks like your kubernetes-dashboard-kong pod is crashing, which is probably causing the access issue. You should check the logs for that specific pod to see what's going wrong. It's common for a CrashLoopBackOff to impact how the service runs.
Have you checked the subnet configuration? The subnet for your client device should match the one used by your Kubernetes nodes. Double-check MetalLB's settings to ensure it doesn't conflict with your router's DHCP range. Your router needs to know where to route packets, especially since you're using MetalLB without BGP.
That makes sense! I didn't realize the subnet overlaps were that significant. I'll look into that.
It can be tricky with networking setups like this. If you're comfortable with it, you might also want to consider route forwarding or VLAN tagging to get everything flowing smoothly. Just make sure whatever changes you make don’t create more conflicts!
Yeah, I saw that too! Make sure to check if there are any configuration errors. Once you sort that out, it might resolve your access issues.