GitOps: Argo CD and Flux · New in v0.3.0

Argo CD and Flux, seen from the objects they manage

PodSteer knows when Argo CD or Flux owns an object. It shows an Application's or a Kustomization's members as the controller itself reports them, and before you change anything a GitOps controller manages, it tells you the change will be reverted on the next sync — and what to do instead.

Download PodSteer All features

The controller's own view

Open an Argo CD Application, a Flux Kustomization or a Flux HelmRelease and PodSteer renders its status, conditions and managed objects as followable rows. Membership is quoted from the controller's own status — never inferred from labels, which double-count and miss things.

The detail panel of an Argo CD Application named guestbook: Synced and Healthy, automated sync with prune and self-heal, its source repository, path guestbook and target revision HEAD, its destination namespace, a successful last sync, and the Service and Deployment it manages, both Synced. The detail panel of an Argo CD Application named guestbook: Synced and Healthy, automated sync with prune and self-heal, its source repository, path guestbook and target revision HEAD, its destination namespace, a successful last sync, and the Service and Deployment it manages, both Synced.
An Argo CD Application, as a typed panel. Sync, health, source and the resources Argo CD manages, quoted from the Application's own status.

A warning at the moment it matters

Every object carries its owner: the header says which Application or Kustomization manages it, and every write dialog says what happens to your change. A rollback on a GitOps-managed Deployment says plainly that the next sync overwrites it, and that the durable fix is a revert in Git.

Pods carry no GitOps marker of their own, so PodSteer follows the owner chain to find the controller above them, and words the warning for what really happens: a change to one pod is not reverted, it is lost when something replaces the pod.

Secrets from External Secrets

A Secret written by the External Secrets Operator is recognised too, with its own sentence: changes are overwritten the next time it refreshes from the external store. The ExternalSecret panel maps remote keys to local keys and reads no values.

Be honest

What it does not do.

  • PodSteer does not sync, refresh or roll back Argo CD Applications itself; it shows what they manage and warns before conflicting changes.
  • A Flux HelmRelease carries no inventory, and its panel says so rather than showing an empty list.
  • Whether Argo CD's self-heal is on lives in the Application; the warning covers both cases rather than guessing.

Read next

Helm releases

Every Helm release and revision, listed from labels alone; one revision's values and manifest read only when you ask.

Day-2 operations

Apply any kind including CRDs, roll back, drain, bulk-act with a review step — and see the kubectl command for each.

Operator panels

Built-in views for cert-manager, KEDA, External Secrets, Argo Rollouts, Trivy, Karpenter, Gateway API and more — no plugin API, nothing to install.

Compared with other tools: PodSteer vs Lens Desktop · PodSteer vs Radar