Blog
What shipped in each release, and how the parts of FleetOps work inside.
FleetOps 1.3: run the server in Kubernetes with HelmA Helm chart and a plain manifest for running FleetOps in your own cluster, with its database on a kept volume and HTTPS for agents.Read the post
Earlier posts
- ReleaseFleetOps 1.4: manage the cluster FleetOps runs inInstalled in Kubernetes, FleetOps registers its own cluster as the local environment through its service account, and a new start page leads straight to adding an environment.
- ReleaseFleetOps 1.1: CVE notificationsEnterprise rules send new vulnerabilities in the images you run to Slack, email, Microsoft Teams, Discord, PagerDuty or a webhook: one message per CVE, batched, with no flood when you start.
- ReleaseFleetOps 1.2: Kubernetes scans pull images like your pods doKubernetes image scans now let the node pull the image through its own registry access or your pull secrets, so private registries such as ECR work without giving FleetOps credentials.
- ReleaseFleetOps 1.0: one image, Community and Enterprise plans, and image scanningFleetOps is 1.0 and follows semantic versioning. There is now one image that runs as Community until a license key turns Enterprise on, the official build is free to run in production, and Enterprise scans every image in the fleet with Trivy.
- ReleaseFleetOps 0.6: Docker Swarm, builds, secrets and git over SSHFleetOps manages Docker Swarm through an agent on every node, with Swarm stacks and roles limited to stacks. Compose stacks can build their images, carry secrets and configs, and follow a git repository over SSH.
- ReleaseFleetOps 0.5: stacks from a git repositoryA stack can take its Compose file from a branch of a git repository. FleetOps syncs it on a push webhook or by polling, then deploys each new version or holds it for review.
- ReleaseFleetOps 0.4: Compose stacks with a plan before every deployWrite a Compose file in the browser and deploy it to any Docker host. See what each deploy changes first, get the stack back as it was if a deploy fails, and roll back to any revision.
- EngineeringHow a remote host joins without opening a portThe FleetOps agent dials out, runs yamux over one WebSocket and hands the server raw streams to the host's Docker socket. Here is why it is built that way.
- ReleaseFleetOps 0.3: backup and restore, single sign-on and LDAPThe whole server in one sealed backup file, free in Community. Enterprise adds single sign-on with Microsoft, Google, GitHub, any OIDC provider or LDAP, and scheduled backups to S3 or a folder.
- EngineeringLive lists without pollingHow FleetOps keeps every open tab current from one Docker event stream per environment, and what it does when a reader falls behind.
- GuideFleetOps as a Portainer alternativeWhere FleetOps fits for teams coming from Portainer, where Portainer is still the better choice, and how to try the two side by side.
- ReleaseFleetOps 0.2: permissions, custom roles and teamsEvery route now checks one named permission. Enterprise adds custom roles, teams and licenses counted by node.
- ReleaseFleetOps 0.1.1: install Helm charts, read custom resourcesHelm install and upgrade with a reviewed plan, every kind the cluster serves, merged workload logs, EKS, GKE and AKS kubeconfigs, and the first Enterprise license.
- ReleaseFleetOps 0.1: a live web UI for Docker and KubernetesThe first release: one small binary that manages Docker, Podman, remote hosts and Kubernetes clusters from the browser, with roles and an audit log.