# liqotech/liqo

Enable dynamic and seamless Kubernetes multi-cluster topologies

Repository: https://github.com/liqotech/liqo
Canonical: https://ross.abutalabs.com/products/liqo
Homepage: https://liqo.io
Language: Go
License: Apache-2.0
License Family: permissive
Topics: kubernetes, liquid-computing, resource-sharing, cloud-computing, multi-cluster, kubernetes-clusters, clusters, k8s
Last push: 2026-08-25T16:01:48+00:00

## Health v2 (maintenance only)
Score: 92/100 (v2, computed 2026-09-02T17:46:02.011165+00:00)
- activity 99, release rhythm 79, longevity 100
- inputs: {"age_days": 2310, "days_push": 8, "days_rel": 61, "gap_med": 76, "n_releases_24m": 10}
- flags: none
- formula: round(0.45*activity + 0.35*rhythm + 0.20*longevity); archived -> min(score, 10)

## Adoption (not part of the score)
Stars 1479, forks 150 (observed 2026-08-28T04:04:50.588535+00:00)

## What it is
Liqo is an open-source project that enables dynamic and seamless Kubernetes multi-cluster topologies across heterogeneous on-premise, cloud, and edge infrastructures. It provides automatic cluster peering, transparent workload offloading to remote clusters via virtual nodes, inter-cluster networking, and cross-cluster storage replication.

## Use cases
- extend kubernetes namespaces across multiple clusters
- offload pods to remote kubernetes clusters transparently
- connect pods across kubernetes clusters without vpn configuration
- share resources between independent kubernetes clusters
- run stateful workloads across multiple clusters
- build hybrid cloud and edge kubernetes topologies
- schedule workloads on remote clusters as a virtual node

## When to choose
- you need multi-cluster kubernetes without complex vpn or certificate setup
- you want transparent workload offloading without modifying applications or kubernetes
- you need cross-cluster pod-to-pod networking independent of CNI plugins
- you operate heterogeneous on-premise, cloud, and edge clusters

## When to avoid
- you only run a single kubernetes cluster
- you need a fully managed multi-cluster solution with vendor support
- your workloads cannot tolerate cross-cluster network latency
- you require strict isolation between clusters with no resource sharing

## Facets
- artifact type: infra-config
- maturity: active
- function: container-orchestration, networking, deployment, scheduling, microservices
- domain: cloud-computing, microservices, infrastructure-as-code
- platform: go, cloud, self-hosted
- tags: multi-cluster, kubernetes-clusters, workload-offloading, cluster-peering, resource-sharing, edge-computing, hybrid-cloud, virtual-kubelet, containers, devops, kubernetes, linux

## Member repositories
- liqotech/liqo (main) score 92

## Provenance
- Observed fields: from GitHub, fetched 2026-08-28T04:04:50.588535+00:00.
- Health v2: computed from the inputs above; adoption is never an input.
- Inferred fields (summary, facets, guidance): AI-extracted, prompt v1, taxonomy v1, on 2026-08-30T04:34:19.475971+00:00, confidence not recorded.
  - readme: https://github.com/liqotech/liqo (fetched 2026-08-28T04:04:50.588535+00:00, sha 02d324c7f938)
  - homepage: https://liqo.io (fetched 2026-08-29T11:41:47.624019+00:00, sha 77953d89c2ea)
- Data as of 2026-08-30T08:39:29.467469+00:00.