gitops-argocd
/gitops-argocd
Use this skill when the user says 'set up argocd', 'gitops with argocd', 'argocd application yaml', 'argocd project', 'ci push vs gitops pull', 'connect ci to argocd', 'argocd image updater', 'first argocd app', 'argocd sso rbac basics'. Sets up a working GitOps pull model with Argo CD: install, AppProject guardrails, first Applications, CI-to-config-repo hand-off, and access control. Do NOT use for: repo layout/promotion strategy across many envs (cloud-native-gitops-workflows), diff/OutOfSync troubleshooting (cloud-native-argocd-reconciliation), HA/sharding/multi-cluster scale (devops-gitops
- Author
- j4flmao ↗
- Repository
- agent-skills ↗
- Licence
- MIT
- Last repository change
- 10.11.2026
Assessment and security
- Files in this package
- 1
- Scripts
- 0
- HTML comments
- 0
- URLs in SKILL.md
- 6
No signals detected. Repository changed on 10.11.2026, without references to retired models or APIs.
MIT, open: use and modify while retaining author attribution.
What it does and when to use it
Use this skill when the user says 'set up argocd', 'gitops with argocd', 'argocd application yaml', 'argocd project', 'ci push vs gitops pull', 'connect ci to argocd', 'argocd image updater', 'first argocd app', 'argocd sso rbac basics'. Sets up a working GitOps pull model with Argo CD: install, AppProject guardrails, first Applications, CI-to-config-repo hand-off, and access control. Do NOT use for: repo layout/promotion strategy across many envs (cloud-native-gitops-workflows), diff/OutOfSync troubleshooting (cloud-native-argocd-reconciliation), HA/sharding/multi-cluster scale (devops-gitops
Triggers from the description
Original author description
Use this skill when the user says 'set up argocd', 'gitops with argocd', 'argocd application yaml', 'argocd project', 'ci push vs gitops pull', 'connect ci to argocd', 'argocd image updater', 'first argocd app', 'argocd sso rbac basics'. Sets up a working GitOps pull model with Argo CD: install, AppProject guardrails, first Applications, CI-to-config-repo hand-off, and access control. Do NOT use for: repo layout/promotion strategy across many envs (cloud-native-gitops-workflows), diff/OutOfSync troubleshooting (cloud-native-argocd-reconciliation), HA/sharding/multi-cluster scale (devops-gitops
How it works
- Purpose
- Agent Protocol
- Push vs Pull
- Install
- AppProject Guardrails
- Application
- CI Hand-off Options
- Access and Security
- Anti-Patterns
- Checklist
SKILL.md preview
---
name: gitops-argocd
description: >
Use this skill when the user says 'set up argocd', 'gitops with argocd', 'argocd application yaml', 'argocd project', 'ci push vs gitops pull', 'connect ci to argocd', 'argocd image updater', 'first argocd app', 'argocd sso rbac basics'. Sets up a working GitOps pull model with Argo CD: install, AppProject guardrails, first Applications, CI-to-config-repo hand-off, and access control. Do NOT use for: repo layout/promotion strategy across many envs (cloud-native-gitops-workflows), diff/OutOfSync troubleshooting (cloud-native-argocd-reconciliation), HA/sharding/multi-cluster scale (devops-gitops-advanced).
version: "2.0.0"
author: "j4flmao"
license: "MIT"
tags: [devops, gitops, argocd, kubernetes, continuous-delivery]
---
# GitOps with Argo CD
## Purpose
Replace "CI runs kubectl against the cluster" with a pull model: CI builds an image and commits its reference to a config repo; Argo CD, running inside the cluster, reconciles the cluster to that repo. CI no longer needs cluster credentials, every change is a reviewed commit, and drift is visible.
## Agent Protocol
### Trigger
"set up argocd", "gitops with argocd", "argocd application", "argocd project", "push vs pull deployment", "connect ci to argocd", "image updater", "argocd rbac".
### Input Context
- Cluster(s), ingress/SSO provider, config repo location and format (Helm/Kustomize/plain).
- Teams and namespaces they own.
### Output Artifact
Install commands, AppProject + Application YAML, CI hand-off step. No file unless requested.
### Response Format
```
Install: {manifest|Helm chart argo/argo-cd}, version pinned
Project: {name} sourceRepos / destinations / allowed kinds
Application(s): {name -> path -> namespace}
Sync: {manual|automated(prune, selfHeal)}
CI hand-off: {commit|PR|image updater}
```
### Completion Criteria
- [ ] Argo CD version pinned; admin password rotated/disabled after SSO.
- [ ] Apps live in a non-`default` AppProject with restricted repos/destinations.
- [ ] CI has no kube credentials.
## Push vs Pull
| | Push (CI deploys) | Pull (GitOps) |
|---|---|---|
| Credentials | CI holds cluster creds | Cluster agent reads Git; CI writes Git only |
| Audit | CI logs | Git history = deploy history |
| Drift | Undetected | Detected; optionally self-healed |
| Rollback | Re-run old pipeline | `git revert` |
## Install
```bash
kubectl create namespace argocd
helm repo add argo https://argoproj.github.io/argo-helm
helm install argocd argo/argo-cd -n argocd --version <pinned-chart-version> \
--set configs.params."server\.insecure"=false
# initial admin password (delete the secret after configuring SSO)
kubectl -n argocd get secret argocd-initial-admin-secret -o jsonpath='{.data.password}' | base64 -d
argocd login argocd.example.com --sso # after Dex/OIDC configured
```
## AppProject Guardrails
```yaml
apiVersion: argoproj.io/v1alpha1
kind: AppProject
metadata:
name: payments
namespace: argocd
spec:
description: Payments team applications
sourceRepos:
- https://github.com/example/platform-config.git
destinations:
- server: https://kubernetes.default.svc
namespace: payments-*
clusterResourceWhitelist: [] # team cannot create cluster-scoped resources
namespaceResourceBlacklist:
- group: ""
kind: ResourceQuota
roles:
- name: deployers
policies:
- p, proj:payments:deployers, applications, sync, payments/*, allow
- p, proj:payments:deployers, applications, get, payments/*, allow
groups: [payments-engineers] # SSO group
```
## Application
```yaml
apiVersion: argoproj.io/v1alpha1
kind: Application
metadata:
name: checkout-dev
namespace: argocd
finalizers:
- resources-finalizer.argocd.argoproj.io # delete app → delete its resources
spec:
project: payments
source:
repoURL: https://github.com/example/platform-config.git
targetRevision: main
path: apps/checkout/overlays/dev
destination:
server: https://kubernetes.default.svc
namespace: payments-dev
syncPolicy:
automated:
prune: true
selfHeal: true
syncOptions:
- CreateNamespace=true
retry:
limit: 5
backoff: { duration: 10s, factor: 2, maxDuration: 3m }
```
Production: often `automated` without `prune` at first, or manual sync with required approvals, until teams trust the flow.
## CI Hand-off Options
1. **CI commit** — after pushing the image, CI updates the image digest in the overlay (`kustomize edit set image`) and commits/opens a PR in the config repo.
2. **Argo CD Image Updater** — watches the registry and writes new tags back to Git (`write-back-method: git`) for matching Applications; good for dev environments.
3. **Webhooks** — configure the Git provider to call `https://argocd.example.com/api/webhook` so Argo CD refreshes immediately instead of waiting for the ~3-minute poll.
## Access and Security
- SSO via OIDC/Dex; RBAC in `argocd-rbac-cm` (`policy.default: role:readonly` or empty).
- Repo credentials as Secrets labelled `argocd.argoproj.io/secret-type: repository` (deploy keys or GitHub App), read-only.
- Secrets: never commit plaintext; use External Secrets Operator / Sealed Secrets / SOPS.
- Restrict who can edit `argocd` namespace objects — Applications in that namespace can target any project they are allowed into.
## Anti-Patterns
- All apps in the `default` project (no restrictions).
- Same repo + branch for app source and deployment config, causing CI loops.
- Mutable image tags in manifests.
- Disabling self-heal and fixing prod with `kubectl edit`.
## Checklist
- [ ] Pinned install, SSO, admin account disabled.
- [ ] AppProjects per team with destination/source limits.
- [ ] CI writes digests to config repo; webhook configured.
- [ ] Notifications (argocd-notifications) for sync failed/degraded.
- [ ] Backup of Argo CD config (`argocd admin export`) or everything declarative in Git.
## References
- Related skills: `skills/devops/argo-cd/SKILL.md`, `skills/cloud-native/gitops-workflows/SKILL.md`, `skills/cloud-native/gitops/SKILL.md`, `skills/devops/ci-cd/github-actions-pipelines/SKILL.md`.
Versions
The database has no other skills named gitops-argocd.
Database snapshot: 13.11.2026 · package version 231d5e652875 (SHA-256 digest of the entire package)
Downloads in the last 30 days: 0 · ranking
Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.
Similar skills
- 100argocd
Deploy Kubernetes apps declaratively with Argo CD applications and projects. Use when tasks mention argocd, Argo CD, argocd app sync, Application CRD, AppProject, or GitOps with Argo CD. - 95cloud-native-gitops-workflows
Use this skill when the user says 'gitops workflow', 'environment promotion', 'app of apps', 'applicationset', 'multi-cluster gitops', 'secrets in gitops', 'sealed secrets', 'external secrets operator', 'gitops repo structure', 'flux vs argocd'. Designs the GitOps operating… - 95cloud-native-argocd-reconciliation
Use this skill when the user says 'argocd reconciliation', 'argocd drift detection', 'why is my app OutOfSync', 'argocd diff', 'ignoreDifferences', 'server-side diff', 'argocd sync waves', 'argocd refresh vs sync', 'argocd application controller internals'. Explains how Argo… - 100argocd
Argo CD GitOps guidance for Kubernetes. Use when Codex needs to install or upgrade Argo CD, design GitOps architecture, author or review Application, AppProject, ApplicationSet, repository, project, RBAC, SSO, Dex, notification, Helm, Kustomize, multi-source, sync wave, hook,… - 96argocd-helper
ArgoCD GitOps deployment management and troubleshooting When user mentions ArgoCD, GitOps, application sync, or argocd commands - 90argocd-gitops-review
Use this skill for Argo CD GitOps review across Application, AppProject, ApplicationSet, sync windows, RBAC, sync impersonation, and Argo CD Agent multi-cluster topologies. Trigger when the user asks whether an Argo CD configuration is safe for production, whether automated sync…