Peer to a foreign cluster

Once Liqo is installed in your cluster, you can start establishing new peerings. This tutorial relies on LAN Discovery since our Kind clusters are in the same L2 broadcast domain.

LAN Discovery

Liqo can automatically discover any available clusters or make any clusters discoverable on the same LAN.

Using kubectl, you can also manually obtain the list of discovered foreign clusters:

kubectl get foreignclusters
ff5aa14a-dd6e-4fd2-80fe-eaecb827cf55   Established              Established              Established         Established             93s

The foreigncluster object is used by Liqo to model the discovered remote clusters, here we can check the status of the interconnection between the two clusters:

  • The Outgoing Peering Phase describes if the local cluster is able to offload pods to the remote one
  • The Incoming Peering Phase describes if the remote cluster is able to offload pods to the local one
  • The Networking Status tells us if there is a network interconnection between the two clusters
  • The Authentication Status tells us if the local cluster has an available identity to operate on the remote one

To check whether Liqo attempts to peer with the foreign cluster automatically, you can check the outgoingPeeringEnabled property of the specific ForeignCluster resource:

kubectl get foreignclusters ${FOREIGN_CLUSTER} --template={{.spec.outgoingPeeringEnabled}}

This command can have three different outcomes:

  • Auto the peering will be active according to the default setting
  • Yes the peering will always be active
  • No the peering will never be active

Peering checking

Presence of the virtual-node

If the peering has succeeded, you should see a virtual node (named liqo-*) in addition to your physical nodes:

kubectl get nodes

NAME                                      STATUS   ROLES
master-node                               Ready    master
worker-node-1                             Ready    <none>
worker-node-2                             Ready    <none>
liqo-9a596a4b-591c-4ac6-8fd6-80258b4b3bf9 READY    agent    <-- This is the virtual node

Verify that the resulting infrastructure works correctly

You are now ready to verify that the resulting infrastructure works correctly, as presented in the next step.