gitops-workflow
Agent workflowswshobson/agentsskills.sh ↗
Installs
10,055
deduplicated, at the last sync
Since we started
+1.1%
40 readings, about 2 hours apart. Not a live curve.
Our category
Agent workflows
ours
Last read
Sep 3, 2026
from the directory
Our brief
oursThis skill provides a comprehensive guide to implementing GitOps workflows using industry-standard tools like ArgoCD and Flux CD. It teaches users how to manage Kubernetes deployments declaratively by storing the desired state in a Git repository. Users can learn to configure sync policies, set up progressive delivery strategies (like Canary or Blue-Green), and implement secure secret management for continuous reconciliation.
- Declarative Kubernetes manifests/YAML configurations
- Setup commands for ArgoCD and Flux CD installations
- Application definitions for GitOps repositories
- A Git repository URL containing desired state configuration
- Kubernetes cluster context
- Tools like kubectl, argocd CLI, or flux CLI
not detected
The evidence provides no information regarding required payment methods or services.
not detected
The evidence provides no information regarding required user registration.
The skill cannot execute the deployments itself, only provide guides and manifests for implementation. It also cannot verify if a cluster is fully compliant with OpenGitOps principles or manage external cloud credentials beyond providing manifest examples.
Evidencestatic findingsplugins/kubernetes-operations/skills/gitops-workflow/references/argocd-setup.md:1-128plugins/kubernetes-operations/skills/gitops-workflow/references/sync-policies.md:1-132plugins/kubernetes-operations/skills/gitops-workflow/SKILL.md:1-290
[{"code":"env_var","match":"GITHUB_CLIENT_SECRET","path":"references/argocd-setup.md"},{"code":"oauth","match":"OAuth","path":"references/argocd-setup.md"}]# ArgoCD Setup and Configuration
## Installation Methods
### 1. Standard Installation
```bash
kubectl create namespace argocd
kubectl apply -n argocd -f https://raw.githubusercontent.com/argoproj/argo-cd/stable/manifests/install.yaml
```
### 2. High Availability Installation
```bash
kubectl apply -n argocd -f https://raw.githubusercontent.com/argoproj/argo-cd/stable/manifests/ha/install.yaml
```
### 3. Helm Installation
```bash
helm repo add argo https://argoproj.github.io/argo-helm
helm install argocd argo/argo-cd -n argocd --create-namespace
```
## Initial Configuration
### Access ArgoCD UI
```bash
# Port forward
kubectl port-forward svc/argocd-server -n argocd 8080:443
# Get initial admin password
argocd admin initial-password -n argocd
```
### Configure Ingress
```yaml
apiVersion: networking.k8s.io/v1
kind: Ingress
metadata:
name: argocd-server-ingress
namespace: argocd
annotations:
cert-manager.io/cluster-issuer: letsencrypt-prod
nginx.ingress.kubernetes.io/ssl-passthrough: "true"
nginx.ingress.kubernetes.io/backend-protocol: "HTTPS"
spec:
ingressClassName: nginx
rules:
- host: argocd.example.com
http:
paths:
- pat# GitOps Sync Policies
## ArgoCD Sync Policies
### Automated Sync
```yaml
syncPolicy:
automated:
prune: true # Delete resources removed from Git
selfHeal: true # Reconcile manual changes
allowEmpty: false # Prevent empty sync
```
### Manual Sync
```yaml
syncPolicy:
syncOptions:
- PrunePropagationPolicy=foreground
- CreateNamespace=true
```
### Sync Windows
```yaml
syncWindows:
- kind: allow
schedule: "0 8 * * *"
duration: 1h
applications:
- my-app
- kind: deny
schedule: "0 22 * * *"
duration: 8h
applications:
- "*"
```
### Retry Policy
```yaml
syncPolicy:
retry:
limit: 5
backoff:
duration: 5s
factor: 2
maxDuration: 3m
```
## Flux Sync Policies
### Kustomization Sync
```yaml
apiVersion: kustomize.toolkit.fluxcd.io/v1
kind: Kustomization
metadata:
name: my-app
spec:
interval: 5m
prune: true
wait: true
timeout: 5m
retryInterval: 1m
force: false
```
### Source Sync Interval
```yaml
apiVersion: source.toolkit.fluxcd.io/v1
kind: GitRepository
metadata:
name: my-app
spec:
interval: 1m
timeout: 60s
```
## Health Assessment
### Custom Health Checks
```yaml
# ArgoC--- name: gitops-workflow description: 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. --- # GitOps Workflow Complete guide to implementing GitOps workflows with ArgoCD and Flux for automated Kubernetes deployments. ## Purpose Implement declarative, Git-based continuous delivery for Kubernetes using ArgoCD or Flux CD, following OpenGitOps principles. ## When to Use This Skill - 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 ## OpenGitOps Principles 1. **Declarative** - Entire system described declaratively 2. **Versioned and Immutable** - Desired state stored in Git 3. **Pulled Automatically** - Software agents pull desired state 4. **Continuously Reconciled** - Agents reconcile actual vs desired state ## ArgoCD Setup ### 1. Installation ```bash # Create namespace kubectl create na
Read 4 of 4 text files in the skill.
Installfrom the directory
npx skills add https://github.com/wshobson/agentsInstalling happens there, not here. We are an index with an opinion, not a mirror.
What is inside itfrom the directory
3 files — names only. The directory does not report sizes.
What the auditors foundfrom the directory
A skill is instructions your agent will follow and scripts it may run, so who checked it matters as much as how many people installed it.
Installs, reading by readingours
Axis starts at 9.9k, not zero — the range is 9.9k to 10.1k.
Asked out loudspoken, not typed
The same skill in the words people use speaking to an assistant rather than typing into a box. Each one carries the situation it came from, and each answer says only what the skill's own files support.
The skill provides guides for setting up both ArgoCD and Flux CD, which are tools used to manage Kubernetes deployments declaratively from a Git repository. It covers everything from initial installation to advanced sync policies.
The evidence does not specify any required paid services or pricing models for implementing these workflows. The guides focus on using standard Kubernetes tooling and Git.
It suggests using tools like External Secrets Operator or Sealed Secrets to keep credentials out of Git and manage them securely. This helps maintain the integrity of your repository.