Try Kubius
⌘K

Power tools

ArgoCD

When a cluster has ArgoCD installed (CRDs in the argoproj.io group), Kubius detects it and surfaces an ArgoCD section in the sidebar with three resource types: Applications, ApplicationSets, and AppProjects.

Applications

The Application list shows sync status (Synced / OutOfSync / Unknown), health (Healthy / Degraded / Progressing / Missing), project, and last sync time.

Application detail tabs

  • Overview - status, source (repo + path + revision + chart/plugin), destination (cluster + namespace), sync policy
  • Resources - every resource ArgoCD is managing for this application, grouped by Kind, with sync + health badges per resource
  • History - deployment history with revision SHA pills
  • Conditions - application-level conditions
  • YAML

Actions

  • Sync - triggers a sync to the target revision (passes prune if auto-prune is enabled)
  • Refresh - soft refresh
  • Hard Refresh - forces ArgoCD to regenerate manifests from source (can be slow for large repos)
  • Terminate Operation - only available during an in-progress sync; stops the sync, leaves already-applied resources in place

The header shows a live indicator while an operation is in progress (Running / Failed / Succeeded badge).

Managed resources

The Resources tab is the most powerful view - every resource ArgoCD touches is listed with its sync + health status. Click any resource to navigate to it in the detail panel; resources Kubius tracks (Pods, Deployments, etc.) are linkable.

A summary banner at the top shows totals: Total / Synced / OutOfSync / Healthy / Degraded / Progressing / Missing.

History

Lists every recorded deployment with timestamp, repo, path, and a revision pill (first 10 chars of the SHA). Each pill has a copy button so you can grab the full SHA.

ApplicationSets

Generators that produce Applications. The detail view shows the generator type (List / Cluster / Git / Matrix / Merge / etc.) and the Applications spawned by the set.

AppProjects

The detail view shows allowed source repos, destinations (clusters + namespaces), allowed cluster-scoped resources, and roles. Useful for understanding which apps are permitted to deploy where.