domains / families / devops / gitops-workflow

gitops-workflow

combined

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. Complete guide to implementing GitOps workflows with ArgoCD and Flux for automated Kubernetes deployments.

When to use

• Implement declarative, Git-based continuous delivery for Kubernetes using ArgoCD or Flux CD, following OpenGitOps principles.
• 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

When not to use

• You need a one-off manual deployment
• You cannot manage cluster access or repo permissions
• You are not deploying to Kubernetes
• Use this skill only when the task clearly matches the scope described above.
• Do not treat the output as a substitute for environment-specific validation, testing, or expert review.
• Stop and ask for clarification if required inputs, permissions, safety boundaries, or success criteria are missing.

Skill page

Conflict

The two copies are nearly identical, but the sickn33 copy changes the Flux installation step from a direct curl-pipe-to-bash to a safer download-and-inspect procedure (and adds a brew alternative). This is a material safety constraint that the rmyndharis copy lacks, so crowning one would hide a real alternative.