A GUI for Your Flux CD Pipeline: See What GitOps Is Actually Doing
If you're running Flux CD, your debugging workflow probably looks something like this:
flux get all -n flux-system
flux get kustomizations
flux get helmreleases -A
kubectl describe kustomization my-app -n flux-system
flux get sources git
# ...still not sure what depends on whatSomething isn't syncing. A Kustomization is stuck, maybe a HelmRelease is failing. You know the answer is somewhere in the dependency chain, but the CLI gives you each piece in isolation. Which GitRepository feeds which Kustomization? Which Kustomization triggers which HelmRelease? You're assembling the picture in your head.
What if you could just see the whole pipeline at once?
Your Entire GitOps Pipeline as a Dependency Graph
Kunobi gives Flux CD something it's never really had: a native graphical interface for your entire GitOps pipeline.
Open the Flux view and you get a live, interactive dependency graph. Every resource Flux manages is a node, color-coded by type. Source repositories appear in red, Kustomizations in indigo, HelmReleases in green, and HelmCharts in amber. These are connected by animated edges that show the direction of flow. Source relationships appear as dashed red lines, deployments as animated green lines, and chart associations as dotted amber.
You can read the shape of your entire pipeline without running a single command. Where things fan out, where they converge, and where something has gone red.
See it in action:
All Your Flux Resources in One Place
Most tools show Flux resources in isolation. Kustomizations on one screen, HelmReleases on another, sources somewhere else. Kunobi brings them together. Open the GitOps section, select the Flux resource tree, and you get every Flux CD resource in your cluster in a single table: HelmReleases, Kustomizations, GitRepositories, OCIRepositories, and more.
From here, filter for a specific app to narrow down to just its resources. Or switch to the flow view to see the dependency graph for whatever you've filtered. This is the starting point for all Flux work in Kunobi, and everything fans out from here.
Tracing a Sync Failure, Visually
Here's where the graph earns its keep. Say you've deployed a change, but nothing is updating. In the terminal, you'd start with flux get kustomizations, check the status, then flux get sources git to see if the source is fetching, then kubectl describe on the Kustomization to read the conditions, then maybe check the HelmRelease too. Four or five commands just to figure out where the chain broke.
In Kunobi, you open the flow view and look for the red node. The whole pipeline is green except for one Kustomization. It's stuck. Click it and you're looking at the full condition history: last attempted revision, reconciliation timestamp, the exact error message. Need to dig deeper? Drill down into the Kustomization to see every resource it manages (Pods, Services, ConfigMaps) and check their status individually.
From the same context menu, you can view logs, open a shell into a container, or scale a deployment. And when you've found the root cause and need to trigger a re-sync, hit Reconcile right there on the node. No terminal switch needed. You can even select multiple resources and reconcile them in bulk, with a progress bar tracking each one.
The whole loop, from "something's wrong" to "here's why" to "fixed and re-syncing," stays inside one view.
Split View: Table and Graph Working Together
The flow graph is great for understanding relationships, but sometimes you need the table for sorting, filtering, or bulk operations. You don't have to choose. Kunobi's split view puts the table on one side and the graph on the other. Click a row in the table and the graph highlights that node. Click a node in the graph and the table scrolls to match. Everything stays in sync.
Your layout preference is remembered across sessions, so you can default to whatever fits the way you work.
Deep Inspection Without the CLI
Click into any Kustomization or HelmRelease and you get status detail that goes well beyond what flux get shows. Last applied revision vs. last attempted revision, so you can see exactly what's deployed compared to what was tried. Full condition history with status, reason, and message for each. Inventory count showing how many resources a Kustomization actually manages. And for GitRepositories, the artifact metadata: commit digest, checkout revision, artifact size, and when it was last fetched.
This is the kind of information that normally takes a kubectl describe plus some YAML parsing. Here it's laid out in a single panel.
Flux and ArgoCD in One View
If your organization runs both Flux and ArgoCD (and this is more common than you'd expect), Kunobi has a unified GitOps Overview that brings resources from both tools into a single table. Each row shows which CD tool manages it, alongside the shared status, namespace, and age columns. One view for everything your GitOps tooling manages, regardless of which tool is doing the managing.
Give It a Try
Flux CD is powerful, but it's always been a terminal-first experience. Kunobi doesn't replace the CLI. It gives you the visual layer that's been missing. See your entire dependency graph at a glance, trace sync failures in seconds instead of minutes, reconcile without switching windows, and inspect conditions and revisions in a single panel.
Kunobi is free to download at kunobi.ninja. Connect to your cluster and see what your Flux pipeline actually looks like.