gitops-workflows

Orchestrate Kubernetes GitOps workflows with ArgoCD and Flux.

194|39|Updated Oct 26, 2025

Search Tags:#secrets #gitops #argocd #flux #multicluster #application-sets #oci-artifacts

Ready to run

npx skills add https://github.com/ahmedasmar/devops-claude-skills --skill gitops-workflows-ahmedasmar

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: gitops-workflows
Source: https://github.com/ahmedasmar/devops-claude-skills/tree/main/gitops-workflows
Command: npx skills add https://github.com/ahmedasmar/devops-claude-skills --skill gitops-workflows-ahmedasmar

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires pyyaml, and includes scripts (resource) and references (resource) and assets (resource) components.

What problem does it solve?

Orchestrates end-to-end GitOps workflows for Kubernetes deployments using ArgoCD and Flux, enabling multi-cluster deployments, secret management, and OCI artifact workflows across environments.

Core Features & Use Cases

Multi-cluster ApplicationSets and hub-spoke patterns for centralized control.
Secrets management with SOPS+age, Sealed Secrets, External Secrets Operator, and OCI-based workflows.
OCI artifacts support for deploying generated configs and Helm charts.
Troubleshooting and drift detection guidance with consolidated reference material.

Quick Start

Set up a GitOps repo with apps/, infrastructure/, and clusters/, bootstrap ArgoCD and Flux with ApplicationSets, and begin multi-cluster deployments.

Frequently Asked Questions about gitops-workflows

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I manage multi-cluster Kubernetes deployments with ArgoCD and Flux?▼

Multi-cluster Kubernetes deployments with ArgoCD and Flux are orchestrated using ApplicationSets and hub-and-spoke topologies. This approach centralizes control across environments by structuring your GitOps repository with dedicated apps, infrastructure, and clusters directories.

What is the best way to handle GitOps secrets across multiple clusters?▼

GitOps secrets across multiple clusters are handled using SOPS with age, Sealed Secrets, External Secrets Operator, or OCI-based workflows. These methods ensure sensitive data is securely managed within your deployment pipelines without exposing plaintext in Git repositories.

Can I use OCI artifacts for deploying Helm charts in a GitOps workflow?▼

OCI artifacts are fully supported for deploying generated configurations and Helm charts in GitOps workflows. This allows you to package, store, and pull deployment artifacts directly from OCI-compliant registries within your ArgoCD or Flux pipelines.

How do I bootstrap a GitOps repository for multi-cluster environments?▼

To bootstrap a GitOps repository for multi-cluster environments, set up directory structures for apps, infrastructure, and clusters, then initialize ArgoCD and Flux with ApplicationSets. This establishes the foundational hub-and-spoke topology for centralized deployment control.

Why does configuration drift happen in GitOps and how can I troubleshoot it?▼

Configuration drift in GitOps happens when live cluster state diverges from the declared Git repository state. Robust troubleshooting and drift detection guidance consolidated within the workflow helps identify, reconcile, and resolve these synchronization discrepancies effectively.