This procedure installs Liqo on your cluster, enabling it to share resources with other Liqo clusters.
This procedure comes in two variants:
kubeadmto install your Kubernetes, or you are running another distribution of Kubernetes (such as K3s).
If your cluster has been installed via
kubeadm, the Liqo Installer can automatically retrieve the parameters required by Liqo to start.
Before installing, you have to properly set the
kubeconfig for your cluster. The Liqo installer leverages
kubectl: by default kubectl refers to the default identity in
~/.kube/config but you can override this configuration by exporting a
You can find more details about configuring
kubectl in the official documentation.
Similarly to WiFi SSID, you can specify a nickname for your cluster by exporting the variable
If you don’t specify one, the installer will give you a cluster name in the form “LiqoClusterX”, where X is a random number.
Your cluster name can be modified after installation as explained here.
Now, you can install Liqo by launching:
curl -sL https://get.liqo.io | bash
If you want to know more about possible customizations, you can show the help message:
curl -sL https://get.liqo.io | bash -s -- --help
If you did not use
kubeadm to install your Kubernetes cluster, or you are running another distribution of Kubernetes (such as K3s), you should explicitly define the parameters required by Liqo, by exporting the following variables before launching the installer:
POD_CIDR: range of IP addresses for the pod network (K3s default: 10.42.0.0/16)
SERVICE_CIDR: range of IP addresses for service VIPs (k3s default: 10.43.0.0/16)
CLUSTER_NAME: nickname for your cluster that will be seen by others. If you don’t specify one, the installer will give you a cluster name in the form “LiqoClusterX”, where X is a random number. Your cluster name can be modified after installation as explained here.
Then, you can run the Liqo installer script, which will use the above settings to configure your Liqo instance.
Please remember to export your K3s
kubeconfig before launching the script, as presented in previous section. For K3s, the kubeconfig is normally stored in
A possible example of installation is the following (please replace the IP addresses with the ones related to your Kubernetes instance):
export KUBECONFIG=/etc/rancher/k3s/k3s.yaml export POD_CIDR=10.42.0.0/16 export SERVICE_CIDR=10.43.0.0/16 curl -sL https://get.liqo.io | bash
Obviously, you should have enough privileges to read the K3s kubeconfig file.
In order to peer with another cluster, you need to have two Kubernetes clusters with Liqo enabled. Therefore you may need to repeat the above procedure on another cluster in order to get a second Liqo instance.
Once you have two clusters ready, you can start the peering procedure, which is presented in the next step.