GitOps and Kubernetes delivery
What is Rancher Fleet? An introduction to SUSE Rancher's GitOps delivery engine for Kubernetes
Rancher Fleet is a container management and deployment engine built around GitOps. It controls and monitors deployments on a single Kubernetes cluster or on large numbers of clusters. Fleet is implemented as Kubernetes CRDs and controllers.
- Tool
- Rancher Fleet
- Made by
- SUSE Rancher
- Official site
- fleet.rancher.io
- Category
- GitOps and Kubernetes delivery
Who makes Rancher Fleet
Rancher Fleet is published by SUSE Rancher. The official website, linked below, is the reference for the project's documentation.
Official website: fleet.rancher.io
What Rancher Fleet is for
Fleet manages what runs on Kubernetes clusters by deploying from Git. It gives users visibility into exactly what is installed on a cluster, which makes it useful when you need to know the real state of a deployment rather than the intended one.
The project also describes Fleet as a distributed initialization system. In that role it is used to customize applications and to manage HA clusters from one point.
Who Rancher Fleet is for
The vendor does not state a specific audience. From its design, Fleet suits teams that deliver applications to Kubernetes through Git and want the same mechanism to work for a single cluster and for many clusters.
Teams that already run Rancher can enable Fleet's experimental features when Fleet is installed with Rancher.
Notable capabilities
Fleet's capabilities center on how it reads sources from Git, how it deploys them, and how it controls the timing of updates.
The bullets below summarize the verified feature set.
- Deploys from Git using raw Kubernetes YAML, Helm charts, Kustomize, or any combination of them.
- Converts all resources into Helm charts, with Helm acting as the deployment engine.
- Runs as Kubernetes CRDs and controllers, and scales from one cluster to many.
- Shows exactly what is installed on a cluster.
- Offers an experimental scheduling feature that defines time windows during which updates to existing deployments are allowed.
- Applies update scheduling at the Cluster level; clusters not associated with any Schedule receive updates immediately.
- Defines Schedule targets the same way as GitRepo targets.
- Keeps experimental features disabled by default; users enable them through extra environment variables when deploying rancher/fleet.
How Rancher Fleet fits GitOps and Kubernetes delivery
In the GitOps and Kubernetes delivery category, Fleet is the part that takes definitions stored in Git and applies them to clusters. Because every resource is converted into a Helm chart, the same deployment path handles plain YAML, Helm and Kustomize inputs.
Within Deployelm's wider niche of CI/CD and deployment platforms, Fleet covers the delivery stage rather than building or testing code. Its scheduling windows add control over when changes reach existing deployments, and the single-to-many cluster model keeps the approach consistent as an environment grows.
Frequently asked questions
What is Rancher Fleet used for?
Fleet is used to control and monitor deployments on a single Kubernetes cluster or on large numbers of clusters, using GitOps. It deploys from Git and shows what is installed on a cluster.
Who develops Rancher Fleet?
Fleet is published by SUSE Rancher.
Does Rancher Fleet support Helm and Kustomize?
Yes. Fleet can deploy from Git using raw Kubernetes YAML, Helm charts, Kustomize, or any combination. Internally, all resources are converted into Helm charts and Helm is the deployment engine.
How does Rancher Fleet schedule updates?
An experimental scheduling feature defines time windows during which updates to existing deployments are allowed. It applies at the Cluster level, and clusters without a Schedule receive updates immediately.
How do I enable Rancher Fleet experimental features?
Experimental features are disabled by default. You enable them through extra environment variables when deploying rancher/fleet, including when Fleet is installed with Rancher.
Deployelm is independent and is not affiliated with SUSE Rancher. Product names belong to their owners. Features change; confirm details on the official website.