Skip to content
Docs · Argo CD

Integrations

Argo CD

Applications, resource trees, diff, sync, history and rollback.

When a cluster serves the Argo CD CRDs, an Argo CD group appears under Administration with Applications, ApplicationSets and Projects. Nothing Argo-related is shown otherwise.

Kubyl showing an Argo CD application's resource tree, sync status and last operation
An application's resource tree with sync status and the last operation.

Applications

The list shows sync and health, running operation, auto-sync, source, revision, destination (a link when it matches one of your contexts) and last sync. Filter by sync status, health, project and destination.

An application tab has Summary, Resources (tree or flat list), Diff, History, Events and Controller logs.

KeysAction
SSync…
RorShiftRRefresh / hard refresh
BRollback…
HHistory
EEdit YAML
CtrlDDelete…
TToggle tree or list (in the application tab)
LorEorDLogs / YAML / diff of the selected node (in the tree)

Sync… offers Dry run, Apply only, Replace, Server-side apply and Selective sync. Delete… lets you choose cascade and requires typing the name. Terminate Operation and Toggle Auto-Sync (when turning it on) ask for confirmation. Argo CD: Open Argo CD UI opens the native UI in a web view or browser.

ApplicationSets and Projects

ApplicationSets show their generators, sync policy and generated apps. Projects show repos, destinations, allow and deny lists, roles and sync windows, including whether one blocks syncing right now.

Kubernetes mode and API mode

Kubernetes mode (default)API mode
Talks toThe Kubernetes API, reading the CRDs.argocd-server.
PermissionsYour Kubernetes RBAC.Argo CD RBAC.
AddsStatus and actions by patching Applications.Rendered diffs, the full resource tree and actions.

Sign in to API mode with Argo CD: Sign In (API Mode)… using SSO, username and password, or an API token. Kubyl first asks you to confirm the detected install (namespace and Service UID). The token is kept in the OS keychain. argocd.api_transport is auto (default), proxy or forward, and argocd.auto_connect (default on) reconnects automatically.

Limitations

  • SSO for OIDC installs needs a cliClientID configured in Argo CD.
  • There is no whole-application rendered-manifest view.
  • Custom health checks written in Lua are visible only in API mode.

Something missing or wrong? Open an issue on GitHub.