gitops-workflows_skill
- Python
9
GitHub Stars
1
Bundled Files
2 months ago
Catalog Refreshed
4 months ago
First Indexed
Readme & install
Copy the install command, review bundled files from the catalogue, and read any extended description pulled from the listing source.
Installation
Preview and clipboard use veilstrat where the catalogue uses aiagentskills.
npx veilstrat add skill nickcrew/claude-cortex --skill gitops-workflows- SKILL.md6.2 KB
Overview
This skill provides expert guidance for implementing production-grade GitOps workflows using ArgoCD and Flux for declarative Kubernetes deployments. It focuses on repository design, secure secret handling, sync and reconciliation policies, progressive delivery patterns, and reliable rollback and promotion strategies. Use it to standardize CI/CD for multi-environment or multi-cluster Kubernetes infrastructures.
How this skill works
The skill breaks GitOps adoption into concrete steps: choose repository structure, select an operator (ArgoCD or Flux), configure secret management, define sync and reconciliation policies, set up environment promotion, and implement progressive delivery and rollback procedures. It explains tool-specific capabilities (ApplicationSets, ImageUpdateAutomation, Rollouts) and maps them to common operational patterns and risk controls.
When to use it
- Implementing GitOps principles for Kubernetes deployments
- Automating continuous delivery from Git repositories
- Managing multi-cluster or multi-environment deployments
- Adopting progressive delivery (canary, blue-green) for risky changes
- Designing secure secret workflows for Git-stored manifests
Best practices
- Treat cluster state as declarative and versioned in Git with clear audit trails
- Never commit unencrypted secrets; use Sealed Secrets, SOPS, or External Secrets
- Automate non-prod sync with prune and self-heal; gate production with approvals
- Design repository structure based on team boundaries and deployment independence
- Add health checks and dependency ordering to avoid partial or broken rollouts
Example use cases
- Set up ArgoCD App of Apps to manage platform-level and app-level manifests across clusters
- Use Flux with ImageUpdateAutomation to automatically promote semver image updates to staging
- Implement canary rollouts with Argo Rollouts or Flagger and a service mesh for traffic shifting
- Create a Git-based promotion flow where CI tags an image and environment overlays pick it up
- Configure External Secrets Operator to sync credentials from Vault or cloud KMS into clusters
FAQ
Choose ArgoCD if you want a UI, strong RBAC and App-of-Apps patterns; choose Flux for a lighter, CLI-native approach with native image automation and deep Kustomize/Helm integration.
How should I handle secrets in GitOps?
Never store plaintext secrets. Use Sealed Secrets for client-side encryption, SOPS with KMS/age for file encryption, or External Secrets to sync from a managed secret store.
