1.3.0 adds a supported way to run the FleetOps server inside Kubernetes. Nothing changes for Docker installs; update the image tag and restart as usual.
The chart
helm install fleetops oci://ghcr.io/pravinbanjade/charts/fleetops --namespace fleetops --create-namespace
The chart is also in a classic repository: helm repo add fleetops https://pravinbanjade.github.io/fleetops. It runs one pod with the Recreate strategy, because the SQLite database lives on the volume, and a 5Gi volume that helm uninstall keeps. The Service has the UI on 9000 and HTTPS on 9443. The server’s own HTTPS listener is on by default, because agents are refused on plain HTTP.
An optional Ingress sends traffic to the HTTPS port by default, so agents still work through it. The TLS certificate, sealing key and Enterprise license come from Secrets you already have. The pod runs as a non-root user with a read-only root filesystem, no capabilities and health probes, and helm test checks the install.
Without Helm, deploy/kubernetes/fleetops.yaml is the chart rendered with its defaults, for a plain kubectl apply. The install guide has both.
In-cluster agents
The command for adding a Kubernetes cluster through an in-cluster agent now carries the certificate FleetOps generated, as the Swarm stack already did. An agent in the same cluster can then dial https://fleetops:9443 without failing on an unknown issuer.
Next
1.4 lets FleetOps manage the cluster it runs in without an agent. See the roadmap.