Blog
What shipped in each release, and how the parts of FleetOps work inside.
How 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.Read the post
Earlier posts
- 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.