Issue with Liqo Installation Inside Helm Package Causing Immediate Namespace Creation and Pending Peering

[fracappa]

I'm trying to run a setup on two kind clusters which are setup through a bash script.

This bash script also includes the installation of a custom helm package I'm developing.

I tried to move Liqo installation inside this helm package, through a pre-install hook job template that is attached to the hostNetwork.

I tried to install liqo either via liqoctl or via helm but I ended up with the same results: once I have liqo installed the two kind clusters already have the liqo-tenant-X namespace related to the other cluster.

This, doesn't happen when moving liqo installation out of the helm package.

I tried to install liqo, setting the flag discovery.config.enableAdvertisement=false. This solved this issue but when I try to run a peering the ForeignCluster Outgoing Peering stays pending:

NAME   TYPE        CLUSTERID                              CLUSTERNAME   OUTGOING PEERING   INCOMING PEERING   NETWORKING   API SERVER    AUTHENTICATION   AGE
kind   OutOfBand   a3d61878-98f7-4d92-b1cb-9b094979adfc   kind          Pending            None               None         Established   Established      73s

So I don't think that this flag solves the issue.

I expect no difference between installing Liqo inside and outside my helm package.

You can clone this repo and run a testbed via: tools/scripts/setup.sh choosing option 1, if you want to reproduce the same setup.

Environment:

• Liqo version: 0.10.3
• Liqoctl version: 0.10.3
• Kubernetes version (use kubectl version): 1.28.0
• Cloud provider or hardware configuration: kind on local machine