-
I'm working on getting a multi-node k3s cluster set up (we've been running single node for awhile now) I think I'm almost there, I can get an agent to join the cluster, pods are scheduled/started on the agent when the server applies new deployments... but the pods can't reach each other as far as I can tell. I tried
I'll try with an image that already has curl installed shortly, although I expect it won't be able to reach the pods either. I launched the server with:
and launched the agent with:
|
Beta Was this translation helpful? Give feedback.
Replies: 2 comments 1 reply
-
The pods are fine on the same node, just not if they are on my agent node. I'm viewing this: #10078 and going to try playing with my Tailscale ACLs |
Beta Was this translation helpful? Give feedback.
-
It was because I was running my <internal screaming> |
Beta Was this translation helpful? Give feedback.
It was because I was running my
k3s server
on a VirtualBox VM and the default Network Adapter isNAT
but it needs to be set toBridged
<internal screaming>