_____ _ ___ | ___| |_ ___ __/ _ \ ___ | |_ | | | | \ \/ / (_) / __| | _| | | |_| |> < \__, \__ \ |_| |_|\__,_/_/\_\ /_/|___/
A K9s-inspired terminal UI for Flux resources, controller health, and GitOps state
flux9s 1.0 is generally available — read the announcement on the Flux blog
Navigating resources, opening details, and running operations
-
Crates.io Downloads
-
GitHub Stars
-
GitHub Downloads
-
Releases
What flux9s is
flux9s is a terminal UI for operators who want live visibility into Flux resources and the cluster state around them without leaving the shell. It watches Flux resources in real time, keeps a local in-memory view of their current state, and lets you move quickly between lists, details, YAML, traces, graphs, and reconciliation history.
The project is intentionally keyboard-first and closely follows familiar K9s patterns: j/k navigation, : command mode, context and namespace switching, footer help, and k9s-style skins.
flux9s is listed as a community UI in the Flux ecosystem.
The problem it solves
The Flux Operator Web UI gives you dashboards in the browser. flux9s is for when you'd rather stay in the terminal; it complements the Web UI rather than replacing it.
Use flux9s to:
- see Flux reconciliation state update live
- inspect Kustomizations, HelmReleases, sources, and Flux Operator resources in one place
- trace ownership chains and visualize managed workloads
- check controller readiness and Flux bundle version from the same interface
- run quick actions such as suspend, resume, reconcile, reconcile-with-source, and delete
Why it stays fast
flux9s uses the Kubernetes Watch API for supported Flux resource types instead of repeatedly polling. It starts in one namespace (flux-system by default) and only watches the whole cluster when you choose all, which keeps API load low on large clusters.
The header uses the same watches to show controller readiness and the installed Flux version.
Built for Flux and Flux Operator
Beyond core Flux controller resources, flux9s also understands Flux Operator resources such as FluxInstance, ResourceSet, ResourceSetInputProvider, and FluxReport. Graph and history views cover them too, and the graph follows the same relationships the Flux Operator Web UI does.
For how the code fits together, see the Developer Guide. If you want to get running quickly, jump to Getting Started.