Advanced peering

In the peer two clusters section of this documentation, we used the liqoctl peer command, which automatically configures all the Liqo modules (namely networking, authentication, and offloading) to create a peering between two clusters. However, there are some cases in which the automatic process is not appropriate, and the user would like to customize advanced parameters, overcome specific network constraints, and more, hence a more granular tuning for the peering process is needed. For instance, we list here some cases in which the automatic peering is not a suitable choice:

• you would like to configure Liqo peering connections via a declarative approach, i.e., with Kubernetes CRs. This is useful to automate the creation and destruction of the Liqo peering connections to enable use cases of GitOps, continuous delivery or integration of Liqo with other services;

• when a peeering connection between different parties need to be created. In that case liqoctl peer automatic peering is not the suitable choice (as designed to support administrators that needs to connect their clusters with Liqo) and the required info and Liqo CRs need to be shared out-of-band and separately applied in each cluster.

• the consumer needs to create multiple requests for resources (ResourceSlice) or you would like to customize how resources are distributed across virtual nodes.

To overcome the above necessities, Liqo allows to configure each module separately, with a more granular control. This section shows how to interact with each individual Liqo module to better tune your peering process.

Prerequirements

We suggest to read this section after you have completed the quick-start guide.

Modules

Check each module specific documentation to understand how to configure it:

• Networking

• Authentication

• Offloading

Furthermore, an additional section describes how to interact with the above modules using Kubernetes CRs, hence using a fully declarative approach.