DevOps / ArgoCD interview questions
What is the ArgoCD CLI and what are the most common commands used day-to-day?
The ArgoCD CLI (argocd) is a command-line tool for interacting with the ArgoCD API Server. It is the primary interface for operators who prefer the terminal over the UI and is also used in CI/CD pipelines for triggering or waiting on syncs.
Before using the CLI, you must log in:
argocd login <argocd-server> --username admin --password <password> # Use --grpc-web if behind an HTTP proxy or load balancer
Common day-to-day commands:
| Command | Purpose |
|---|---|
argocd app list | List all Applications with sync and health status |
argocd app get <app> | Show detailed status, sync info, and resource tree for an Application |
argocd app sync <app> | Trigger a sync; add --prune to allow pruning, --dry-run to preview |
argocd app wait <app> | Block until the Application reaches a target health/sync state (useful in CI) |
argocd app diff <app> | Show the diff between live cluster state and Git desired state |
argocd app rollback <app> <id> | Roll back to a specific sync history revision |
argocd app set <app> --helm-set key=val | Override Helm values at the Application level without changing Git |
argocd cluster list | List all registered clusters |
argocd proj list | List all AppProjects |
In CI/CD pipelines, the typical pattern is: build image → push image → update Git tag → argocd app wait <app> --health to block the pipeline until ArgoCD confirms the deployment is healthy.
Which CLI command is most useful in a CI/CD pipeline to block execution until a deployment is healthy?
What does the --dry-run flag do in argocd app sync?
More Related questions...
