You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm trying to create a k8s cluster with k0s edge nodes behind NAT (basically in peoples homes), with a couple k8s clusters at AWS that should act as the "router" for all the k8s nodes.
The setup looks like this:
home1: kilo.squat.ai/location=home1
home2: kilo.squat.ai/location=home2
home3: kilo.squat.ai/location=home3
aws nodes: kilo.squat.ai/location=aws
kg config: --mesh-granularity=location
my problem is that kilo thinks that there should be a wireguard connection be created between home1, home2 and home3, but this is not possible because of the NAT case.
So I'm trying to find a solution where the home nodes only create a wireguard connection to the aws leader
Added a picture for clarity, how the topology looks today and I would like to get rid of connections crossed as red.
The text was updated successfully, but these errors were encountered:
I'm trying to create a k8s cluster with k0s edge nodes behind NAT (basically in peoples homes), with a couple k8s clusters at AWS that should act as the "router" for all the k8s nodes.
The setup looks like this:
kilo.squat.ai/location=home1
kilo.squat.ai/location=home2
kilo.squat.ai/location=home3
kilo.squat.ai/location=aws
kg config:
--mesh-granularity=location
my problem is that kilo thinks that there should be a wireguard connection be created between home1, home2 and home3, but this is not possible because of the NAT case.
So I'm trying to find a solution where the home nodes only create a wireguard connection to the aws leader
Added a picture for clarity, how the topology looks today and I would like to get rid of connections crossed as red.
The text was updated successfully, but these errors were encountered: