macOS
Homebrewverified · 100%
brew install fleet-clilocal Homebrew formula metadata
brew / rank 4800
Install fleet-cli with Homebrew, zypper, Nix
Manage large fleets of Kubernetes clusters. Version 0.16.0 via Homebrew; verified 2026-07-26. Also installable with zypper: sudo zypper install fleet-cli.
install
Additional install commands
Linux
openSUSE zypperverified · 92%
sudo zypper install fleet-cliopenSUSE Tumbleweed package metadata · fleet-cli · source: download.opensuse.org
Nixverified · 92%
nix profile install nixpkgs#fleetnixpkgs package indexes · pkgs/by-name/fl/fleet/package.nix · source: api.github.com
overview
Package summary
Manage large fleets of Kubernetes clusters
Project links
Commands and aliases
- fleet
history
Project history and usage
Fleet CLI is the command-line tool for Rancher Fleet, a Kubernetes GitOps and HelmOps system for deploying workloads from Git and local bundle sources across one or many clusters. The package matters because it exposes Fleet bundle creation, targeting, diffing, deployment, and diagnostics as a standalone binary.
Project history
The rancher/fleet repository was created in 2020. The upstream README describes Fleet as GitOps and HelmOps at scale, designed for many clusters while still lightweight enough for a single cluster.
Fleet's design turns raw Kubernetes YAML, Helm charts, Kustomize trees, or combinations of those sources into Helm-backed deployments, emphasizing control, consistency, visibility, and auditability. The CLI documentation positions the `fleet` binary as a way to create, preview, target, and deploy bundles from local files without always requiring a GitRepo.
Adoption history
Fleet is part of the Rancher/SUSE Kubernetes management ecosystem, so its adoption is tied to multi-cluster Kubernetes operations rather than a general-purpose developer CLI audience. The supplied package metadata records Homebrew, Nix, and zypper packaging, which matches its role as an operator/admin tool installed on workstations and CI environments.
How it is used
Fleet CLI can create bundles from Helm charts, Kubernetes manifests, Kustomize directories, and `fleet.yaml` files. Documented commands include `fleet apply` for creating or previewing bundles, `fleet target` for evaluating cluster targeting rules, and `fleet deploy` for applying a targeted bundle to a cluster.
`fleet.yaml` adds bundle options; the docs state that any directory containing `fleet.yaml` is automatically turned into a bundle. The file can define namespace behavior, Helm options, Kustomize settings, target customizations, rollout behavior, dependencies, and monitoring ignore rules.
Why package nerds care
Fleet CLI is package-nerd significant as a packaged Kubernetes control-plane companion: it is not the controller itself, but a local binary that lets operators inspect and reproduce Fleet's bundle pipeline. That makes it useful for debugging GitOps state, packaging release artifacts, and validating cluster targeting before controller reconciliation.
Timeline
- 2020: rancher/fleet repository created.
- 2020s: Fleet documentation presents the project as GitOps and HelmOps at scale for Kubernetes clusters.
- 2020s: Fleet CLI documentation describes standalone local bundle workflows with `fleet apply`, `fleet target`, and `fleet deploy`.
- 2026: v0.15.x release line is current in the official documentation and GitHub releases metadata.
Related projects
- Rancher and SUSE provide the broader Kubernetes management context.
- Helm, Kustomize, Kubernetes manifests, GitRepo resources, Bundle resources, fleet-controller, fleet-agent, and fleet-examples are central related components in the official docs.
Sources
- https://api.github.com/repos/rancher/fleet
- https://fleet.rancher.io/
- https://fleet.rancher.io/how-tos-for-users/install-use-fleet-cli
- https://fleet.rancher.io/reference/ref-fleet-yaml
- https://formulae.brew.sh/formula/fleet-cli
- https://github.com/rancher/fleet
- https://raw.githubusercontent.com/rancher/fleet/master/README.md
security posture
Risk level: orange
infrastructure mutation or orchestration signal.
Risk classifier
orange risk · medium confidence · infrastructure
Why
- infrastructure mutation or orchestration signal
Signals
- text:kubernetes,cluster
Install behavior
- No Homebrew bottle metadata was recorded.
Recommended review
Before unattended agent use, check whether the tool reads plaintext credentials, writes remote state, publishes artifacts, or shells out to plugins.
local files
Configuration and credential file locations
These source-backed paths show where this package keeps local settings or durable credentials. Automic Vault can use them as review targets for secret scanning, migration, and command approval.
Configuration files
Config paths the tool may read or write during local use.
- Unix
fleet.yaml
executables
Installed executables
| Command | Kind | Exposure | Note |
|---|---|---|---|
fleet | executable | indexed executable | Discovered from the local executable index. |
freshness
Version and freshness
These signals separate page generation age, package-manager activity, and upstream release comparison. Version lag is warned only when an evidence URL and comparable versions are present.
page generated2026-08-03
manager version0.16.0
manager updated2026-07-26
local dataunknown
upstreamnot available
latest detectednot detected
- okNo freshness warnings were generated.
install metadata
Package metadata
| Package key | brew:fleet-cli |
|---|---|
| Version | 0.16.0 |
| Package manager | Homebrew |
| Homepage | https://fleet.rancher.io/ |
| Repository | https://github.com/rancher/fleet |
| Last updated | 2026-07-26T11:37:57+02:00 |
| Pulse | updated |
| Bottle | not recorded |
| Service | none declared |
source database matches
Other package-manager records
Matches are pulled from external package-manager indexes and kept separate from local Automic Vault package links.
zypper95%
fleet-cli 0.16.0-1.2
CLI for the Rancher Fleet GitOps tooling
https://github.com/rancher/fleet
sudo zypper install fleet-cli- License: Apache-2.0
- Category: Unspecified
- Architecture: x86_64
- Source Package: fleet-cli
- 1 dependencies
- 2 provides
- normalized package name match
- Matched by: Fleet Cli
zypper95%
fleet-cli-bash-completion 0.16.0-1.2
Bash Completion for fleet-cli
https://github.com/rancher/fleet
sudo zypper install fleet-cli-bash-completion- License: Apache-2.0
- Category: System/Shells
- Architecture: noarch
- Source Package: fleet-cli
- 2 dependencies
- 1 provides
- normalized package name match
- Matched by: Fleet Cli
zypper95%
fleet-cli-fish-completion 0.16.0-1.2
Fish Completion for fleet-cli
https://github.com/rancher/fleet
sudo zypper install fleet-cli-fish-completion- License: Apache-2.0
- Category: System/Shells
- Architecture: noarch
- Source Package: fleet-cli
- 2 dependencies
- 1 provides
- normalized package name match
- Matched by: Fleet Cli
zypper95%
fleet-cli-zsh-completion 0.16.0-1.2
Zsh Completion for fleet-cli
https://github.com/rancher/fleet
sudo zypper install fleet-cli-zsh-completion- License: Apache-2.0
- Category: System/Shells
- Architecture: noarch
- Source Package: fleet-cli
- 2 dependencies
- 1 provides
- normalized package name match
- Matched by: Fleet Cli
Nix92%
fleet
nix profile install nixpkgs#fleet- installed executable or alias match
- Matched by: Fleet
source trail
Generated from repository data
This page is generated by av-web from the private package SQLite artifact built by scripts/generate-pkg-sqlite.py.
Combined YAML source
View the package source record on GitHub.
Used sources
- Geiger risk classifier
- cross-ecosystem install command graph
- curated configuration and credential file locations
- curated package history
- external package-manager database matches
- pkg.so package database
- pkgdb category and tag curation