Open garymm opened 1 month ago
I'm seeing this again. I tried upgradng to 1.64.2 (latest helm chart) and deleting all the pods and this time I can't figure out a way to fix it.
Restarting the kubernetes host seems to have fixed it, at least for now.
What is the issue?
I'm really not sure how to reproduce this but I've seen this a couple of times. Restarting the tailscale ingress pods seems to fix it.
I set up two services (docker-registry, and headlamp) with type ClusterIP both listening on port 80. Both services have a tailscale ingress. This is a test cluster with only one node, so everything is on the same node.
When trying to connect, I see errors like this in the tailscale pod:
Restarting the tailscale ingress pod seems to fix the issue.
I'm not a kubernetes expert, but it seems supicious that tailscale is trying to connect to the service on 127.0.0.1:80 rather than using the cluster IP.
I am able to connect to both services simultaneously using
kubectl port-forward
, so I'm pretty sure this is not an inherit limitation of my kubernetes set-up.Steps to reproduce
No response
Are there any recent changes that introduced the issue?
No response
OS
Linux
OS version
kubernetes
Tailscale version
1.62.1
Other software
calico CNI
Bug report
BUG-893cd6c8f00a44fda54bd05672e58e601316cc21d2892024305ff3afa3f4c675-20240509231821Z-5c7d259ff6d31521