| name | building-gitops-workflows |
| description | Execute use when constructing GitOps workflows using ArgoCD or Flux. Trigger with phrases like "create GitOps workflow", "setup ArgoCD", "configure Flux", or "automate Kubernetes deployments". Generates production-ready configurations, implements best practices, and ensures security-first approach for continuous deployment.
|
| allowed-tools | Read, Write, Edit, Grep, Glob, Bash(kubectl:*), Bash(git:*) |
| version | 1.22.0 |
| author | Jeremy Longshore <jeremy@intentsolutions.io> |
| license | MIT |
| tags | ["devops","deployment","kubernetes","security"] |
| compatibility | Designed for Claude Code, also compatible with Codex and OpenClaw |
Building GitOps Workflows
Overview
Construct GitOps workflows using ArgoCD or Flux to implement declarative, Git-driven continuous delivery for Kubernetes. Generate Application/Kustomization manifests, configure sync policies, set up multi-environment promotion, and implement RBAC and notification integrations.
Prerequisites
- Kubernetes cluster accessible via
kubectl with admin permissions
- Git repository for storing Kubernetes manifests (separate from application code recommended)
- ArgoCD or Flux installed on the cluster, or Helm charts ready for installation
- Container images built and pushed to a registry accessible from the cluster
- SSH key or access token for Git repository authentication from the cluster
Instructions
- Choose the GitOps tool based on requirements: ArgoCD for UI-driven management, Flux for lightweight Git-native approach
- Design the repository structure:
environments/{dev,staging,prod}/ with Kustomize overlays or Helm values per environment
- Generate ArgoCD Application or Flux Kustomization manifests pointing to the Git repository path for each environment
- Configure sync policy: enable
automated.selfHeal and automated.prune for non-production; use manual sync for production
- Set up Git repository credentials as a Kubernetes Secret for the GitOps operator
- Implement environment promotion: update the image tag in staging manifests, test, then promote to production via PR
- Configure notifications: Slack/email alerts on sync success, failure, or health degradation via ArgoCD Notifications or Flux Alert Provider
- Add RBAC: restrict who can sync production applications and who can modify GitOps configurations
- Validate the setup: push a manifest change to Git and verify the GitOps operator detects and applies it within the sync interval
Output
- ArgoCD Application or Flux Kustomization manifests per environment
- Git repository structure with Kustomize bases and overlays
- RBAC configuration (ArgoCD AppProject, Kubernetes RBAC)
- Notification configuration (Slack webhooks, email)
- CI pipeline step to update image tags in the GitOps repository after build
Error Handling
| Error | Cause | Solution |
|---|
ComparisonError: Failed to load target state | Invalid manifest path or Git ref |
