RE: Submariner natting issues
11 views
Skip to first unread message
Vaishnavi Rajulu
Oct 4, 2024, 5:59:31 AM10/4/24
to submariner-users
Hi Guys,
I have broker in rke2 cluster with public ip.
I am joining a kubeadm cluster and kind cluster(both are in private ips) to the broker.
In broker:
✓ Showing Connections
GATEWAY CLUSTER REMOTE IP NAT CABLE DRIVER SUBNETS STATUS RTT avg.
k8-worker1 kubeadm 10.x.x.x no libreswan 242.2.0.0/16 connected 1.376351ms
kind-control-plane kind 59.x.x.x yes libreswan 242.1.0.0/16 connecting 0s
kubeadm natting is false and it straightly connects through the private ip whereas in kind the natting is true and it connected through the natted public ip?
Why is this difference and why kind is in connecting state?
GATEWAY CLUSTER REMOTE IP NAT CABLE DRIVER SUBNETS STATUS RTT avg.
k8-worker1 kubeadm 10.x.x.x no libreswan 242.2.0.0/16 connected 1.376351ms
kind-control-plane kind 59.x.x.x yes libreswan 242.1.0.0/16 connecting 0s
kubeadm natting is false and it straightly connects through the private ip whereas in kind the natting is true and it connected through the natted public ip?
Why is this difference and why kind is in connecting state?
Reply all
Reply to author
Forward
0 new messages