Agent skill · software engineering · aiskillstore
gitops-workflow
Implement GitOps workflows with ArgoCD and Flux for automated, declarative Kubernetes deployments with continuous reconciliation. Use when implementing GitOps practices, automating Kubernetes deployments, or setting up declarative infrastructure management.
Why this skill is useful
Provides specific commands and configurations for implementing GitOps workflows with ArgoCD and Flux that the AI wouldn't reliably generate on its own.
What it needs
Requires flux, kubectl installed locally. About 3k tokens when loaded. Last updated 2026-08-07. 405 stars on the source repository.
What this skill does
GitOps Workflow Complete guide to implementing GitOps workflows with ArgoCD and Flux for automated Kubernetes deployments. Purpose Implement declarative, Git-based continuous delivery for Kubernetes using ArgoCD or Flux CD, following OpenGitOps principles. When to Use This Skill Set up GitOps for Kubernetes clusters Automate application deployments from Git Implement progressive delivery strategies Manage multi-cluster deployments Configure automated sync policies Set up secret management in GitOps OpenGitOps Principles 1. Declarative - Entire system described declaratively 2. Versioned and Immutable - Desired state stored in Git 3. Pulled Automatically - Software agents pull desired state 4. Continuously Reconciled - Agents reconcile actual vs desired state ArgoCD Setup 1. Installation Reference: See references/argocd-setup.md for detailed setup 2. Repository Structure 3. Create Application 4. App of Apps Pattern Flux CD Setup 1. Installation 2. Create GitRepository 3. Create Kustomization Sync Policies Auto-Sync Configuration ArgoCD: Flux: Reference: See references/sync-policies.md Progressive Delivery Canary Deployment with ArgoCD Rollouts Blue-Green Deployment Secret Management External Secrets Operator Sealed Secrets Best Practices 1. Use separate repos or branches for different environments 2. Implement RBAC for Git repositories 3. Enable notifications for sync failures 4. Use health checks for custom resources 5. Implement approval gates for production 6. Keep secrets out of Git (use External Secrets) 7. Use App of Apps pattern for organization 8. Tag releases for easy rollback 9. Monitor sync status with alerts 10. Test changes in staging first Troubleshooting Sync failures: Out of sync status: Related Skills k8s-manifest-generator - For creating manifests helm-chart-scaffolding - For packaging applications
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills aiskillstore/gitops-workflow--8c6ac0