Blog

Releasev0.1.1

FleetOps 0.1.1: install Helm charts, read custom resources

Helm 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.

0.1.1 is mostly about Kubernetes. Update the image tag and restart; the database migrates on start.

Helm install and upgrade

Start the server with --helm-binary helm and Install chart appears on the Helm releases page, with Upgrade on each release. Give it a repository URL and chart name, or an oci:// reference, a version and values.

FleetOps renders the chart with that helm, without touching the cluster. It then shows every object it will create, change or delete, the values diff, the hooks in order and the chart’s notes. Nothing is applied until you confirm. Install and upgrade hooks run, and Jobs and Pods they start are waited for. FleetOps writes release history the way Helm does, so helm history and helm rollback keep working from the CLI.

Every kind the cluster serves

Custom Resources in the sidebar lists the CRDs and, per API group, every other kind found by API discovery. A custom resource’s list shows the columns its CRD declares for kubectl get, follows the cluster live and sorts rows by their Ready condition. A CRD installed a moment ago shows up at once. ReplicaSets, HPAs, network policies, storage and RBAC kinds also got pages of their own.

Logs for a whole workload

A Deployment’s logs are now one stream across all its pods, each line tagged with its pod. Pods that come and go are followed live, and a restarted container’s previous run is one click away. A terminal can be opened from a workload in the pod and container you pick.

EKS, GKE and AKS kubeconfigs

Kubeconfigs whose user runs an exec plugin are accepted when the server starts with --kube-exec-plugins=default. FleetOps runs aws eks get-token, gke-gcloud-auth-plugin or kubelogin itself, with a 30-second limit, no terminal and an environment that cannot redirect code loading. This suits FleetOps running as a binary on a machine that is already signed in.

The Enterprise edition starts

The Enterprise image, fleets/fleetops-ee, reads a signed license file offline. Its first feature is audit export. The Enterprise code is source-available in the same repository, under ee/; Community never depends on it. See Open source for how the two are licensed.

0.1.2 followed a day later with one fix: charts that carry their own CRDs install correctly under Helm 3.