Reputation: 3
I followed the tutorial on https://piotrminkowski.com/2021/10/25/kubernetes-multicluster-with-kind-and-cilium/ to create two separate Cilium clusters, kind-c1 and kind-c2, on two different VMs within the same network. However, when attempting to connect them using the cilium clustermesh connect command, I encountered an error stating that the remote and local clusters have the same, non-unique name: c1.
I am unsure if it is even possible to connect Cilium Clustermesh between two separate VMs in this way. Has anyone successfully accomplished this and can offer guidance on how to resolve this error?
ā
Cluster access information is available:
- <IP1>:2379
ā
Service "clustermesh-apiserver" of type "LoadBalancer" found
š Cluster Connections:
š Global services: [ min:0 / avg:0.0 / max:0 ]
ubuntu@vm2$ sudo cilium clustermesh status --context kind-c1
ā
Cluster access information is available:
- <IP2>:2379
ā
Service "clustermesh-apiserver" of type "LoadBalancer" found
š Cluster Connections:
š Global services: [ min:0 / avg:0.0 / max:0 ]
how to connect this with cilium clustermesh
but when i try to connect it
ubuntu@vm1$ sudo cilium clustermesh connect --destination-endpoint <IP2>:2379
āØ Extracting access information of cluster c1...
š Extracting secrets from cluster c1...
ā¹ļø Found ClusterMesh service IPs: [<IP1>]
āØ Extracting access information of cluster c1...
š Extracting secrets from cluster c1...
ā¹ļø Found ClusterMesh service IPs: [<IP2>]
Error: Unable to connect cluster: remote and local cluster have the same, non-unique name: c1
Upvotes: 0
Views: 421
Reputation: 1
Each cluster must be assigned a unique name and cluster identification. See documentation: https://docs.cilium.io/en/v1.9/gettingstarted/clustermesh/#prepare-the-clusters
Upvotes: -1