1.4.0 makes a Kubernetes install useful from the first login. Update the image tag or the chart and restart; the database migrates on start. 1.4.1 followed on 2026-11-18 and only moved links to the fleetops.run domain.
The cluster FleetOps runs in
When FleetOps starts inside a cluster and no Docker socket answers, it registers that cluster as the local environment, reached through the pod’s service account. There’s no agent and no kubeconfig to manage, and the token rotates on its own.
The Helm chart now binds that service account to cluster-admin by default. Set rbac.clusterRole to edit or view to limit what FleetOps can do in its own cluster, or rbac.create=false to keep the token out of the pod. If you delete the environment, add it back from Admin → Environments → Add environment → Kubernetes → The cluster FleetOps runs in.
Upgrade note: if your own values set serviceAccount.automount: false, also set rbac.create: false (or turn automount on), or the upgrade stops with a message saying so.
A start page that leads somewhere
An admin with no environments now sees Add your first environment, with a button that opens the form. Before, the page suggested mounting a Docker socket, which doesn’t exist on Kubernetes or on a bare server.
Bare servers
With neither Docker nor a cluster, the server now starts with no environments, and manages remote hosts, swarms and clusters through agents. That suits a small VM that only runs FleetOps.
A starter for Helm values
deploy/helmfile/ holds a short values.yaml with the settings most installs change (public URL, ingress, TLS, license, sealing key, storage, resources) and a helmfile.yaml pinned to a chart version. Each release also attaches the chart’s full default values as fleetops-values.yaml.
Next
Port-forward, then API tokens, SIEM forwarding and long audit retention for Enterprise. See the roadmap.