Refresh, sync, restart, rollback
The four operations worth having on a phone, from the list row menu or the detail page — including a history picker for rollbacks.
The same four actions are available from an application’s row menu in the list and from the app-bar menu on its detail page, so you never have to navigate to act.
Refresh
Ask ArgoCD to re-read the source repository and recompute the diff. This is the “did my merge land?” button — it answers whether ArgoCD has noticed a change, separately from whether it has applied one.
Sync
Apply the desired state. The row’s sync status then tracks the operation live over the watch stream, so you can watch it go Synced (or fail) without polling.
Restart workloads
A rolling restart of the workloads the application manages — the ArgoCD-side equivalent of restarting a Deployment from the Kubernetes tab, useful when the fix is “pick up the new config” rather than “change anything”.
Rollback
The one that matters when a deploy has gone wrong. Kubo opens a history picker listing the application’s previous revisions — each with its revision id and deploy time — and rolls back to the one you choose.
The whole flow (picker sheet and the rollback call) is shared code, so it behaves identically whether you start from the list or from the detail page. Like every state-changing action in the app, it confirms first.
What is deliberately missing
There is no “edit the application manifest” and no “create app” flow. Kubo is built for the operations you want to perform away from a laptop, and authoring GitOps configuration is not one of them.
Back to ArgoCD.