Clusternet vs kOps

Clusternet is a free, open-source add-on for managing Kubernetes clusters across public and private cloud, hybrid, on-premises, and edge environments. It lets operators manage member clusters from a parent cluster and access them as though they were local. It deploys Kubernetes resources, custom resource definitions, and Helm charts, with configuration tailored to individual clusters. Application scheduling can replicate workloads or distribute them by cluster weight or available capacity. Clusternet supports clusters from AWS, Google Cloud, Tencent Cloud, and Alibaba Cloud, along with on-premises systems, k3s, and edge clusters. It can discover and register clusters created by Cluster API and configure network tunnels for clusters in VPC networks, at the edge, or behind a firewall. Dynamic RBAC rules control access to managed clusters, and Submariner integration can connect workloads across clusters. Installation options include Helm and manual setup. A kubectl plugin is available through Krew or as a binary. Linux builds are listed for several architectures. Clusternet is a CNCF Sandbox project.

kOps is a free, open-source tool for creating, upgrading, maintaining, and destroying production-grade, highly available Kubernetes clusters. It also provisions the cloud infrastructure those clusters require, with the control plane managed by the customer. AWS and Google Cloud are officially supported; DigitalOcean, Hetzner, and OpenStack are in beta, while Azure is in alpha.

Configuration uses a YAML manifest-based API with templating and dry-run modes. State synchronization supports dry runs and automatic idempotency, and kOps can generate Terraform. It offers popular CNI networking providers out of the box and supports ARM64 architectures. kOps runs on Linux, macOS, and Windows; kubectl is required to install and use it. SSH access to masters and nodes is allowed from any address by default, although no public key is installed by default. SSH sources can be restricted in cluster configuration or with a command option. The security documentation says Pods can access the underlying instance IAM role and describes its permission scope as broad. The project points users to public office hours and Kubernetes Slack channels for support.