@LavredisG Can you add the subctl diagnose and subctl gather outputs? Which CNI are you using?

The first screenshot appended in the issue creation is the failing part of the subctl diagnose all command, anything else was green ticked. I am using kindnet as CNI. Here is the subctl gather output.

Hi,

Does things work for you when you use 2 clusters?
Can you try deploying Kind clusters using Submariner and check if it helps?

Submariner will use https://github.com/submariner-io/shipyard/blob/devel/scripts/shared/lib/clusters_kind to create the clusters if I am not mistaken, but I have different yaml files for my clusters specific to my use case, so I wouldn't want to use the test clusters.

What CNI do you use?
can you elaborate on your Kind configuration?

What CNI do you use? can you elaborate on your Kind configuration?

kindnet used by default when creating kind clusters. What info would further help you?

Ack,

It seems like some environment configuration error.

A. Can you check if you get the same behavior when deploying Kind clusters using Submariner ?,we'll have a reference point
B. I usually apply [1] script on my host before deploying Submariner on Kind, can you check it?

[1]
`sudo setenforce 0
sudo sysctl fs.inotify.max_user_watches=524288
sudo sysctl fs.inotify.max_user_instances=512

sudo systemctl stop firewalld
sudo systemctl disable firewalld
sudo dnf install -y iptables-services
sudo touch /etc/sysconfig/iptables
sudo touch /etc/sysconfig/ip6tables
sudo systemctl start iptables
sudo systemctl start ip6tables
sudo systemctl enable iptables
sudo systemctl enable ip6tables
sudo iptables -t filter -F
sudo iptables -t filter -X
sudo sysctl net.bridge.bridge-nf-call-iptables=0
sudo sysctl net.bridge.bridge-nf-call-arptables=0
sudo sysctl net.bridge.bridge-nf-call-ip6tables=0
sudo systemctl restart docker`

If I have to recreate my clusters I could try this, atm I can't do that because it would take down my whole setup.