Clusternet

Clusternet is an open-source add-on that gives Kubernetes teams a parent-cluster control point for fleets spanning cloud, private infrastructure, on-premises sites, and the edge. It is best for operators who need coordinated deployment and scheduling across multiple clusters rather than a single-cluster console. The zero-cost model is compelling, but release-specific Kubernetes compatibility and operational setup requirements deserve attention before adoption.

Overview

Clusternet centralizes access to managed clusters through a parent cluster, presenting them to operators as though they were local. That approach can make a geographically or organizationally dispersed fleet easier to administer, provided the team is already comfortable with Kubernetes administration and cluster lifecycle concerns.

Its scope covers public-cloud clusters from AWS, Google Cloud, Tencent Cloud, and Alibaba Cloud, along with private and on-premises installations, certified distributions such as k3s, and edge clusters. Customer-managed control planes suit organizations that need to retain infrastructure ownership, but also leave installation, upgrades, and day-to-day reliability with the operator.

Key features

Application delivery supports Kubernetes native resources, custom resource definitions, and Helm charts, including OCI-based charts. Cluster-specific configuration lets one application definition be adapted to different member clusters instead of copied into separate workflows. Automatic discovery and registration of clusters created through Cluster API can reduce manual enrollment in environments already using that project.

Scheduling offers replication, static distribution based on cluster weight, and dynamic distribution based on cluster capacity. Replication fits workloads that should run across the fleet; weighted placement supports deliberate allocation; capacity-based placement is better when available resources vary between clusters.

Network tunnels can be configured for clusters in VPC networks, at the edge, or behind a firewall. Integration with Submariner is documented for securely connecting workloads across member clusters, extending the platform beyond control-plane access alone.

Dynamic RBAC governs visits to managed clusters. The AppPusher feature gate can be disabled on an agent where child-cluster security concerns make application pushing undesirable. A kubectl plugin is installable through Krew or as a downloadable binary, and a client-go wrapper supports programmatic integration.

Installation paths include Helm and manual procedures, with separate guidance for k3s. The project also provides community help through its mailing list, CNCF Slack channel, Google Group, GitHub issues, and developer discussion spaces. Clusternet is identified as a CNCF Sandbox project.

Pricing

Clusternet (open source): free

This is an open-source project with no paid plans or stated usage limits. It fits teams that can operate customer-managed infrastructure and want multi-cluster management without subscription charges. The trade-off is that the free plan does not shift operational responsibility to a vendor, so installation, maintenance, compatibility checks, and support remain part of the team's workload.

Platforms

Clusternet is available through an API on Linux and in self-hosted deployments. Linux builds are listed for amd64, arm64, ppc64le, s390x, 386, and arm, giving it a broad range of server and edge hardware targets.

Compatibility needs careful planning: Clusternet manages Kubernetes versions above v1.17.x, with compatibility documented by Clusternet release, and versions below v0.13.0 have no guaranteed support for Kubernetes versions above v1.24.0. Quick-start documentation also warns that several kind clusters with many pods can hit inotify resource limits and prevent pods from starting.

Who it's for

Clusternet is a strong fit for platform teams running public, private, hybrid, on-premises, or edge Kubernetes fleets that want one parent-cluster operating model. It is particularly useful when deployments must be replicated or placed according to weights or capacity, and when cluster-specific Helm or resource configuration matters.

It is less suitable for organizations seeking a hosted control plane, a polished single-cluster dashboard, or vendor-managed lifecycle operations. Teams with older Clusternet releases or large local test environments should validate compatibility and system limits before standardizing.

Pros and cons

Pros

• Broad environment coverage: one management model spans major cloud providers, on-premises, k3s, and edge clusters.
• Flexible application placement: replication, weighted static distribution, and capacity-aware scheduling address different fleet policies.
• Open integration surface: Helm, CRDs, OCI charts, Cluster API discovery, Submariner, kubectl, and client-go support varied workflows.
• No stated usage ceiling: the open-source plan costs nothing without published paid tiers or quotas.

Cons

• Operator-owned overhead: self-hosting means the team handles installation, upgrades, and reliability.
• Version-sensitive support: older Clusternet releases lack guaranteed support for newer Kubernetes versions.
• Setup pitfalls: resource limits such as inotify exhaustion can disrupt dense kind-based quick starts.

Alternatives

Choose Kubermatic Kubernetes Platform instead if you want an open-source Community Edition with broader API, desktop, web, and operating-system coverage, plus a separately priced Enterprise Edition.

vCluster Platform is the better choice when virtual clusters and a freemium model, including a free tier with stated CPU/GPU and high-availability limits, match your architecture.

Pick Cluster API when the priority is an open-source Kubernetes project for cluster lifecycle APIs and provider components rather than Clusternet's centralized fleet access.

Portainer suits teams wanting a web-capable management interface and a free Business Edition tier for up to three nodes.

Consider kOps for Kubernetes cluster operations across Linux, macOS, and Windows without paid plans.

KubeSphere is an alternative open-source container platform with a Community Edition.

openCenter offers a free, self-supported Community plan from Rackspace Technology.

Rancher is worth considering for its open-source platform and optional Rancher Prime offering.

See the Kubernetes Management Platforms list for more options.

Verdict

Choose Clusternet if you run Kubernetes across varied environments and want centralized, policy-driven deployment and scheduling without subscription cost. Its main reason to look elsewhere is the operational and compatibility burden of a customer-managed, release-sensitive platform; teams wanting hosted management or a more turnkey interface should evaluate alternatives first.