Tool cheatsheet
Argo CD 3 Cheatsheet
Install Argo CD, define Applications declaratively, and manage sync, diffs, history and rollbacks with the argocd CLI.
Install and log in
- Install Argo CD — Create a namespace and apply the official manifests. Pin to a release tag for production instead of stable.
- Reach the UI — Forward the API server to your machine, then open https://localhost:8080.
- Get the initial admin password — Print the generated password for the admin account, then change it and delete the initial secret.
- Log in with the CLI — Log in to the API server. Add --grpc-web if the server sits behind a proxy that doesn't pass gRPC.
- Change the admin password — Set a new password for the signed-in account.
Applications
- Create an application — Deploy a path of a Git repository into a namespace. Argo CD tracks the repository and compares it to the cluster.
- List applications — Show applications with their sync and health status.
- Inspect an application — Show an application's resources, sync status and health.
- See what would change — Compare the Git state with the live cluster before syncing.
- Sync an application — Apply the Git state to the cluster.
- Turn on automated sync — Sync automatically when Git changes. prune deletes resources removed from Git, and selfHeal reverts manual changes.
- See deployment history — List the revisions that were synced.
- Roll back — Return to an earlier deployed revision by its history ID. Disable auto-sync first or it will sync forward again.
- Delete an application — Delete the application, and with --cascade its resources, from the cluster.
- Read pod logs — Show logs from the application's pods.
Declarative setup
- Define an Application in YAML — Keep applications in Git too. This one deploys a Helm chart folder with automated sync.
- Generate applications from a list — An ApplicationSet creates one Application per element, for example per environment.
- Create it from the file — Apply the Application manifest to the argocd namespace.
- Create a project — Projects limit which repositories, clusters and namespaces applications may use.
Repositories and clusters
- Add a private repository — Register credentials for a private Git repository. Use a token, not your password.
- List repositories — Show configured repositories and their connection status.
- Register another cluster — Add a cluster from your kubeconfig context so Argo CD can deploy to it.
- List clusters — Show clusters Argo CD can deploy to.
- Refresh from Git — Make Argo CD re-read the repository without waiting for the polling interval.
- Useful sync options — Create the namespace, replace resources that can't be patched, or sync in a prune-last order.
Related cheatsheets
- Ansible 2 cheatsheet — Run ad-hoc commands and playbooks, manage inventories, roles, collections and secrets with Ansible.
- AWS CLI 2 cheatsheet — Configure credentials and manage S3, EC2, Lambda, logs, containers and secrets with the AWS CLI v2.
- Azure CLI 2 cheatsheet — Sign in and manage resource groups, VMs, web apps, storage, Kubernetes, registries and secrets with the az command.
- Bash and Linux 5 cheatsheet — Everyday shell and Linux commands for files, searching text, permissions, processes and servers.
- Claude API cheatsheet — Call Claude from Python, TypeScript or curl: messages, streaming, thinking, tools, structured output, caching, batches and error handling.
- Claude Code cheatsheet — Run Claude Code in the terminal: starting sessions, slash commands, permissions, CLAUDE.md, hooks, MCP servers and headless use.