Fleet

Fleet keeps Kubernetes clusters in sync with a Git repo, and it was built for the case where you have a lot of clusters. Put raw YAML, Helm charts, or Kustomize in Git and Fleet deploys it to one cluster or a large fleet, turning everything into Helm releases under the hood. Apache 2.0, free, and made by Rancher, now part of SUSE.

You need a Kubernetes cluster and Helm already. Install is two Helm charts. For many clusters you run a manager cluster plus an agent in each downstream cluster. The agents pull from the manager, so clusters behind NAT or on private networks work without inbound access. That pull design is why it suits edge deployments. It also comes preinstalled in Rancher as Continuous Delivery.

Solo and small teams with one or two clusters: free, but argoproj/argo-cd and fluxcd/flux2 are the more common picks, and Argo CD ships its own web UI. Medium and large teams already on Rancher: use it, it is already there. Paid support means SUSE Rancher Prime, and SUSE does not publish the price.

The catch: it is still 0.x with v1alpha1 APIs after six years. At scale the bottleneck is etcd, because stored objects grow as clusters times bundles. The docs warn against polling Git at scale and admit a GitRepo can get stuck in a Failed state under high load.