Argocd gitops review
Skill Raishin/vanguard-frontier-agentic/skills/argocd/argocd-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 should be enabled, whether prune+selfHeal is appropriate, whether AppProject scope is too wide, or how to enforce least-privilege sync identity.From its SKILL.md
npx -y skills add Raishin/vanguard-frontier-agentic --skill argocd-gitops-reviewAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
SKILL.md
3.6 KB, 680 tokens by cl100k_base, as published. Nobody here has run it
Argo CD GitOps Review
Purpose
Review Argo CD Application, AppProject, ApplicationSet, sync windows, RBAC, and the central argocd-cm / argocd-rbac-cm configuration against blast radius, drift handling, and least-privilege sync identity. Argo CD's controller defaults to cluster-admin permissions on every destination cluster — the security posture lives in AppProject boundaries, sync impersonation, and explicit RBAC, not in the controller defaults.
Lean operating rules
- Prefer live cluster evidence (
kubectl get applications,appprojects,applicationsets -n argocd -o yamlplus theargocd-cmandargocd-rbac-cmConfigMaps) when the active client exposes it; otherwise fall back to official Argo CD documentation and sanitized YAML from the user. - Separate confirmed facts from inference. If sync history, current health, or RBAC binding state was not queried, say so.
- Treat
application.sync.impersonation.enabled: false(default) in production as a critical finding — every sync runs as the controller's cluster-admin ServiceAccount. - Treat
AppProjectwithsourceRepos: ['*']anddestinations: ['*']as a wide-blast-radius finding — any commit in any repo can deploy anywhere. - Treat
automated.prune: true+automated.selfHeal: trueon production Applications as critical without an explicit allowlist of authorized Git refs and a tested rollback runbook — Git divergence becomes irreversible deletion. - Challenge
ApplicationSetgenerators that include unbounded clusters (clusters: {}) or label selectors with no exclusion — one mis-labeled cluster joins the rollout. - Challenge
syncOptions: ['Replace=true']andsyncOptions: ['ServerSideApply=false']on stateful resources — Replace deletes-then-creates, breaking PVC bindings. - Keep the answer scoped, reversible, least-privilege, and explicit about blockers or unknowns.
References
Load these only when needed:
- Evidence path and tooling — use when choosing live cluster evidence, confirming Argo CD install state and version, or switching to documentation mode.
- Workflow and output contract — use when executing the full review, applying stress checks on Application / AppProject / ApplicationSet, or formatting the final answer.
- Official sources — use when you need the detailed Argo CD documentation list, RBAC syntax, and grounded insights from the project.
Response minimum
Return, at minimum:
- the scoped target (
Application,AppProject,ApplicationSet, orargocd-rbac-cmpolicy) and evidence level, - the sync identity (controller default cluster-admin, impersonated ServiceAccount, or
destinationServiceAccount), - the blast radius assessment (
sourceRepos,destinations,clusterResourceWhitelist,namespaceResourceBlacklist), - the drift handling posture (
automated,prune,selfHeal,syncWindows), - the safest next actions and rollback plan,
- the assumptions or blockers that prevent stronger conclusions.
What ships with it: 4 files
18.7 KB alongside SKILL.md
references/
- mcp-and-evidence.md2.9 KB
- official-sources.md5.0 KB
- workflow-and-output.md9.3 KB
- metadata.json1.5 KB