playbooks

home / skills / pluginagentmarketplace / custom-plugin-devops / gitops

gitops skill

/skills/gitops

This skill helps you automate deployment and infrastructure with GitOps workflows using ArgoCD, FluxCD, and declarative manifests.

npx playbooks add skill pluginagentmarketplace/custom-plugin-devops --skill gitops

Review the files below or copy the command above to add this skill to your agents.

Files (8)
SKILL.md
797 B
---
name: gitops
description: GitOps practices with ArgoCD, FluxCD, and declarative infrastructure management
sasmp_version: "1.3.0"
bonded_agent: 05-cicd-automation
bond_type: SECONDARY_BOND
---

# GitOps Skill

## MANDATORY
- GitOps principles and workflows
- ArgoCD installation and configuration
- Application manifests and sync
- Kustomize and Helm integration
- Sync policies and strategies

## OPTIONAL
- FluxCD and Flux v2
- Image automation and updates
- Multi-cluster management
- Secrets management with SOPS
- Progressive delivery (Argo Rollouts)

## ADVANCED
- Custom health checks
- ApplicationSets for multi-tenancy
- Disaster recovery strategies
- GitOps for non-Kubernetes workloads
- Enterprise GitOps patterns

## Assets
- See `assets/gitops-patterns.yaml` for ArgoCD templates

Overview

This skill teaches GitOps practices for deploying and managing infrastructure and applications using ArgoCD, FluxCD, and declarative manifests. It focuses on continuous delivery workflows, application sync, and integrating Kustomize and Helm for templated deployments. The content balances pragmatic install/config steps with higher-level patterns like progressive delivery and multi-cluster management.

How this skill works

The skill inspects and guides setup of GitOps pipelines: repository layout, ArgoCD installation and configuration, and application manifests. It explains sync policies and strategies, integrates Kustomize and Helm into application definitions, and shows how to use ApplicationSets for multi-tenancy. Optional modules cover Flux v2, image automation, SOPS secrets, and progressive delivery with Argo Rollouts.

When to use it

  • Adopting declarative CI/CD where Git is the single source of truth
  • Deploying to Kubernetes clusters with automated sync and drift detection
  • Managing multiple clusters or tenant environments from a central repo
  • Automating image updates and rollouts for frequent releases
  • Implementing secure secrets handling and progressive delivery patterns

Best practices

  • Keep repository layout consistent: separate apps, infrastructure, and bootstrap repos
  • Use pull requests and branch protection to approve changes to the desired state
  • Prefer declarative templates (Kustomize/Helm) and avoid imperative scripts in runtime
  • Define clear sync policies and health checks to prevent unsafe automated rollouts
  • Store secrets encrypted (SOPS) and use short-lived credentials for controllers

Example use cases

  • Install ArgoCD and create an Application that syncs a Kustomize overlay to a staging cluster
  • Use ArgoCD ApplicationSet to deploy the same app across multiple clusters or namespaces
  • Configure Flux v2 image automation to update HelmRelease values when new container images are published
  • Implement canary rollouts with Argo Rollouts and automated promotion on success
  • Build disaster recovery playbooks using git-backed manifests and automated cluster bootstrap

FAQ

Should I use ArgoCD or Flux for GitOps?

Both are mature; choose ArgoCD for a strong UI and Application-centric workflows, or Flux for lightweight, Git-native controllers and tighter Helm automation.

How do I handle secrets in Git?

Encrypt secrets with SOPS and keep decryption keys in a secure secret store or use controller-level secret providers to avoid plaintext in Git.