Freedom251 › Container Networking Software
Liqo

What Liqo is
Liqo is free, open-source software for linking Kubernetes clusters and coordinating resources across them. It lets a consumer cluster extend namespaces to remote clusters, carrying configurations, secrets, services, and other resources along. A remote cluster can appear as a virtual node, giving the consumer cluster a way to schedule workloads there; Liqo also describes support for running stateful workloads with storage across clusters.
Peered clusters form resource and service relationships, while a network fabric connects their pods through WireGuard VPN tunnels by default. Peering can be declared with Kubernetes resources and managed through GitOps tools such as ArgoCD. The liqoctl command-line tool handles installation and removal, peering, namespace-level offloading, and status reporting, with downloads for Linux, macOS, and Windows.
Liqo is designed for varied on-premises, cloud, edge, and multi-cloud Kubernetes environments. Listed platforms include Kubernetes, Kubeadm, K3s, K0s, AKS, EKS, GKE, Aruba Cloud KaaS, and OpenShift. It requires Linux kernel 5.10 or later, and its documentation suggests a cluster with at least 2 CPUs and 2 GB of RAM. Compatibility is guaranteed for the latest three Kubernetes major releases. The project is licensed under Apache-2.0 and directs users to documentation, GitHub, and its Slack community.
Who it suits
Liqo suits teams that need to connect Kubernetes clusters across on-premises, public cloud, edge, or multi-cloud environments. It is relevant when workloads, namespace resources, and pod networking need to span peered clusters, including stateful workloads using cross-cluster storage.
What it does well
- Free and open source under the Apache-2.0 license.
- Extends namespaces and replicates resources across clusters.
- Schedules workloads on remote clusters through virtual nodes.
- Connects pods with WireGuard VPN tunnels by default.
- Supports declarative peering and GitOps management with ArgoCD.
What to know first
- Requires Linux kernel 5.10 or later.
- Compatibility is guaranteed only for the latest three Kubernetes major releases.
- ServiceAccount tokens can propagate to remote clusters unless API-server support is disabled.
Getting started
- Visit https://liqo.io/ and consult the project documentation.
- Check that the cluster uses Linux kernel 5.10 or later and has at least 2 CPUs and 2 GB of RAM.
- Use the liqoctl download for Linux, macOS, or Windows.
- Install Liqo and configure peering with liqoctl or Kubernetes resources.
- Configure namespace-level offloading and review status with liqoctl.
Verdict
Choose Liqo if you need free, open-source tooling to peer Kubernetes clusters and share namespace resources or workload capacity across them. Look elsewhere if your environment cannot meet its Linux kernel requirement or depends on officially supported Kubernetes releases older than the latest three major versions.
Questions
Does Liqo cost anything?
Liqo is free and open source, licensed under Apache-2.0.
Which environments and platforms does it support?
It is designed for heterogeneous on-premises, public cloud, edge, and multi-cloud Kubernetes environments. Listed platforms include Kubernetes, Kubeadm, K3s, K0s, AKS, EKS, GKE, Aruba Cloud KaaS, and OpenShift.
Which operating systems have liqoctl downloads?
The liqoctl CLI provides downloads for Linux, macOS, and Windows.
What are the system and Kubernetes requirements?
Liqo requires Linux kernel 5.10 or later, and its documentation suggests at least 2 CPUs and 2 GB of RAM for the cluster. Compatibility is guaranteed for the latest three Kubernetes major releases; older releases may work but are not officially supported.
How does Liqo secure cross-cluster connections?
Connections use WireGuard VPN tunnels by default. Documentation also describes generating a kubeconfig with limited permissions for peering.
Can ServiceAccount tokens be sent to remote clusters?
Liqo can propagate ServiceAccount tokens to remote clusters. The documentation describes disabling API-server support if this is a security concern.
Facts from Liqo's own pages
- CLI platforms
- The liqoctl CLI provides downloads for Linux, macOS, and Windows. · docs.liqo.io, 4 Oct 2026
- Compatibility limit
- Liqo guarantees compatibility with the latest three Kubernetes major releases; older releases may work but are not officially supported. · docs.liqo.io, 4 Oct 2026
- Integrations
- The installation guide describes using Helm 3 to install Liqo, and the CLI supports kubectl-style Kubernetes API access. · docs.liqo.io, 9 Oct 2026
- Kubernetes support
- Liqo is guaranteed compatible with the latest three Kubernetes major releases; older releases may work but are not officially supported. · docs.liqo.io, 9 Oct 2026
- License
- The official site says Liqo is licensed under Apache-2.0. · liqo.io, 9 Oct 2026
- Management tool
- The liqoctl CLI installs and uninstalls Liqo, manages peering, configures namespace-level offloading, and reports status. · docs.liqo.io, 9 Oct 2026
- Namespace extension
- Liqo can extend consumer namespaces across clusters and replicate configurations, secrets, services, and other resources. · liqo.io, 4 Oct 2026
- Networking
- Liqo provides cross-cluster pod-to-pod and pod-to-service connectivity across different CNI configurations, using secured network tunnels for cross-cluster traffic. · docs.liqo.io, 9 Oct 2026
- Peering
- Liqo automatically establishes peer-to-peer resource and service relationships between independent clusters. · docs.liqo.io, 9 Oct 2026
- Purpose
- Liqo is an open-source project for creating dynamic Kubernetes multi-cluster topologies across on-premise, cloud, and edge infrastructures. · docs.liqo.io, 9 Oct 2026
- Requirements
- Liqo requires Linux kernel 5.10 or later and recommends at least 2 CPUs and 2 GB of RAM for the cluster. · docs.liqo.io, 4 Oct 2026
- Security
- The requirements page says the network gateway uses WireGuard over UDP and the Kubernetes API server uses HTTPS over TCP. · docs.liqo.io, 9 Oct 2026
- Security configuration
- Liqo can propagate ServiceAccount tokens to remote clusters, and the documentation describes disabling API-server support if this is a security concern. · docs.liqo.io, 9 Oct 2026
- Storage
- Liqo’s storage fabric supports remote execution of stateful workloads using a data-gravity approach. · docs.liqo.io, 9 Oct 2026
- Support
- The official site links to Liqo’s documentation, quick-start guide, and community Slack. · liqo.io, 9 Oct 2026
- Supported environments
- The official site says Liqo supports on-premise, public cloud, edge, and multi-cloud environments, including managed or self-hosted Kubernetes distributions. · liqo.io, 9 Oct 2026
- System requirements
- Liqo requires Linux kernel 5.10 or later and the documentation suggests a cluster with at least 2 CPUs and 2 GB of RAM. · docs.liqo.io, 9 Oct 2026
- Workload offloading
- Liqo can offload workloads to remote clusters without requiring changes to Kubernetes or the applications. · docs.liqo.io, 9 Oct 2026
Where Liqo stands on Freedom251
- Container Networking Software#12 of 28