How do I install the CI CD Gitops Kubernetes skill?

Run npx skillmds@latest add irahardianto/ci-cd-gitops-kubernetes in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is CI CD Gitops Kubernetes safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with CI CD Gitops Kubernetes?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is CI CD Gitops Kubernetes free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published CI CD Gitops Kubernetes?

irahardianto (@irahardianto) published this skill. Their other Agent Skills are listed on their SkillMD profile.

CI CD Gitops Kubernetes by irahardianto

Name: CI CD Gitops Kubernetes
Author: irahardianto

File contents

CI/CD — GitOps and Kubernetes Deployment

Supplement to @.gemini/skills/ci-cd-principles/SKILL.md (Level 2). Apply only for K8s or K8s-based platforms. Not for Docker Compose or serverless.

Strategy Selection

Strategy	When	Trade-off
Rolling	Default; SLO requirements	Simple, mixes versions briefly
Blue-Green	Zero-downtime, instant rollback	Doubles infra during switch
Canary	Risk-reducing incremental; A/B	Requires traffic splitting

Rolling (Default)

strategy:
  type: RollingUpdate
  rollingUpdate:
    maxSurge: 25%
    maxUnavailable: 0%    # Zero-downtime

Rules: maxUnavailable: 0 for prod SLO. Set minReadySeconds. Configure terminationGracePeriodSeconds for in-flight requests.

Blue-Green

Blue (v1) [LIVE 100%] → Green (v2) [STANDBY]
        ↕ Switch LB
Blue (v1) [STANDBY]   → Green (v2) [LIVE 100%]

Rules: identical infra. Smoke test green before switch. Keep blue alive ≥30 min post-switch. DB migrations must be backward-compatible.

Canary

 5% → canary (v2), 95% → stable (v1)
25% → canary,      75% → stable    [metrics good]
100% → canary (now stable)          [bake time passes]

Rules: define success metrics before rollout. Auto-rollback if canary error rate >2× baseline. Min bake 15–30 min per increment. Feature flags complement canary for functional testing.

GitOps

App Repo (code) → CI builds image → updates tag in Config Repo
Config Repo (K8s manifests) → ArgoCD/Flux syncs to cluster

Rules: git = single source of truth. All prod changes via PRs on config repo (no kubectl in prod). ArgoCD/Flux auto-corrects drift. Secrets reference external stores — never plaintext in git.

apiVersion: argoproj.io/v1alpha1
kind: Application
metadata:
  name: myapp-production
spec:
  source:
    repoURL: https://github.com/org/config-repo
    path: environments/production/myapp
    targetRevision: HEAD
  destination:
    server: https://kubernetes.default.svc
    namespace: production
  syncPolicy:
    automated:
      prune: true
      selfHeal: true

Secrets Management

Tool	Pattern
External Secrets Operator	Syncs from AWS/GCP/Vault → K8s Secrets
Sealed Secrets	Encrypts with cluster key; safe to commit
Vault Agent Injector	Sidecars inject at runtime

Checklist

Deploy strategy defined + documented
maxUnavailable: 0 for prod SLO
terminationGracePeriodSeconds configured
GitOps (no kubectl apply in prod CI)
Config repo separate from app repo
Config PRs require review before sync
Secrets in external store, not plaintext
Rollback tested + documented

CI/CD Principles @.gemini/skills/ci-cd-principles/SKILL.md
Security Principles GEMINI.md § Security Principles
Monitoring @.gemini/skills/monitoring-and-alerting-principles/SKILL.md
Feature Flags @.gemini/skills/feature-flags-principles/SKILL.md

---name: ci-cd-gitops-kubernetesdescription: Kubernetes deployment and GitOps patterns: rolling/blue-green/canary strategies, ArgoCD/Flux manifests, K8s secrets management. Supplement to ci-cd-principles.---## CI/CD — GitOps and Kubernetes Deployment> Supplement to `@.gemini/skills/ci-cd-principles/SKILL.md` (Level 2). Apply only for K8s or K8s-based platforms. Not for Docker Compose or serverless.### Strategy Selection| Strategy | When | Trade-off ||---|---|---|| Rolling | Default; SLO requirements | Simple, mixes versions briefly || Blue-Green | Zero-downtime, instant rollback | Doubles infra during switch || Canary | Risk-reducing incremental; A/B | Requires traffic splitting |### Rolling (Default)```yamlstrategy: type: RollingUpdate rollingUpdate: maxSurge: 25% maxUnavailable: 0% # Zero-downtime```Rules: `maxUnavailable: 0` for prod SLO. Set `minReadySeconds`. Configure `terminationGracePeriodSeconds` for in-flight requests.### Blue-Green```Blue (v1) [LIVE 100%] → Green (v2) [STANDBY] ↕ Switch LBBlue (v1) [STANDBY] → Green (v2) [LIVE 100%]```Rules: identical infra. Smoke test green before switch. Keep blue alive ≥30 min post-switch. DB migrations must be backward-compatible.### Canary``` 5% → canary (v2), 95% → stable (v1)25% → canary, 75% → stable [metrics good]100% → canary (now stable) [bake time passes]```Rules: define success metrics before rollout. Auto-rollback if canary error rate >2× baseline. Min bake 15–30 min per increment. Feature flags complement canary for functional testing.### GitOps```App Repo (code) → CI builds image → updates tag in Config RepoConfig Repo (K8s manifests) → ArgoCD/Flux syncs to cluster```Rules: git = single source of truth. All prod changes via PRs on config repo (no `kubectl` in prod). ArgoCD/Flux auto-corrects drift. Secrets reference external stores — never plaintext in git.```yamlapiVersion: argoproj.io/v1alpha1kind: Applicationmetadata: name: myapp-productionspec: source: repoURL: https://github.com/org/config-repo path: environments/production/myapp targetRevision: HEAD destination: server: https://kubernetes.default.svc namespace: production syncPolicy: automated: prune: true selfHeal: true```### Secrets Management| Tool | Pattern ||---|---|| External Secrets Operator | Syncs from AWS/GCP/Vault → K8s Secrets || Sealed Secrets | Encrypts with cluster key; safe to commit || Vault Agent Injector | Sidecars inject at runtime |### Checklist- [ ] Deploy strategy defined + documented- [ ] `maxUnavailable: 0` for prod SLO- [ ] `terminationGracePeriodSeconds` configured- [ ] GitOps (no `kubectl apply` in prod CI)- [ ] Config repo separate from app repo- [ ] Config PRs require review before sync- [ ] Secrets in external store, not plaintext- [ ] Rollback tested + documented### Related- CI/CD Principles @.gemini/skills/ci-cd-principles/SKILL.md- Security Principles GEMINI.md § Security Principles- Monitoring @.gemini/skills/monitoring-and-alerting-principles/SKILL.md- Feature Flags @.gemini/skills/feature-flags-principles/SKILL.md

Frequently asked questions

CI CD Gitops Kubernetes