// Production-grade DevOps patterns with Kubernetes 1.34+, Terraform 1.9+, Docker 27+, ArgoCD/FluxCD GitOps, SRE, eBPF-based observability, AI-driven monitoring, CI/CD security, and cloud-native operations (AWS, GCP, Azure, Kafka).
| name | ops-devops-platform |
| description | Production-grade DevOps patterns with Kubernetes 1.34+, Terraform 1.9+, Docker 27+, ArgoCD/FluxCD GitOps, SRE, eBPF-based observability, AI-driven monitoring, CI/CD security, and cloud-native operations (AWS, GCP, Azure, Kafka). |
This skill equips Claude with actionable templates, checklists, and patterns for building self-service platforms, automating infrastructure with GitOps, deploying securely with DevSecOps, scaling with Kubernetes, ensuring reliability through SRE practices, and operating production systems with AI-driven observability.
Modern Best Practices (December 2025): Kubernetes 1.34 (in-place Pod resource updates GA, 1.35 releasing Dec 17), Docker 27 with BuildKit optimizations, Terraform 1.9+ with improved provider ecosystem, ArgoCD 2.14/FluxCD 2.5 GitOps patterns, eBPF-based observability (Cilium, Hubble), and AI-driven AIOps for incident correlation.
| Task | Tool/Framework | Command | When to Use |
|---|---|---|---|
| Infrastructure as Code | Terraform 1.9+ | terraform plan && terraform apply | Provision cloud resources declaratively |
| GitOps Deployment | ArgoCD / FluxCD | argocd app sync myapp | Continuous reconciliation, declarative deployments |
| Container Build | Docker 27+ | docker build -t app:v1 . | Package applications with dependencies |
| Kubernetes Deployment | kubectl / Helm (K8s 1.34+) | kubectl apply -f deploy.yaml / helm upgrade app ./chart | Deploy to K8s cluster, manage releases |
| CI/CD Pipeline | GitHub Actions | Define workflow in .github/workflows/ci.yml | Automated testing, building, deploying |
| Security Scanning | Trivy / Falco | trivy image myapp:latest | Vulnerability scanning, runtime security |
| Monitoring & Alerts | Prometheus + Grafana | Configure ServiceMonitor and AlertManager | Observability, SLO tracking, incident alerts |
| Load Testing | k6 / Locust | k6 run load-test.js | Performance validation, capacity planning |
| Incident Response | PagerDuty / Opsgenie | Configure escalation policies | On-call management, automated escalation |
| Platform Engineering | Backstage / Port | Deploy internal developer portal | Self-service infrastructure, golden paths |
What do you need to accomplish?
├─ Infrastructure provisioning?
│ ├─ Cloud-agnostic → Terraform (multi-cloud support)
│ ├─ AWS-specific → CloudFormation or Terraform
│ ├─ GCP-specific → Deployment Manager or Terraform
│ └─ Azure-specific → ARM templates or Terraform
│
├─ Application deployment?
│ ├─ Kubernetes cluster?
│ │ ├─ Simple deploy → kubectl apply -f manifests/
│ │ ├─ Complex app → Helm charts
│ │ └─ GitOps workflow → ArgoCD or FluxCD
│ └─ Serverless?
│ ├─ AWS → Lambda + SAM/Serverless Framework
│ ├─ GCP → Cloud Functions
│ └─ Azure → Azure Functions
│
├─ CI/CD pipeline setup?
│ ├─ GitHub-based → GitHub Actions (template-github-actions.md)
│ ├─ GitLab-based → GitLab CI
│ ├─ Enterprise → Jenkins or Tekton
│ └─ Security-first → Add SAST/DAST/SCA scans (template-ci-cd.md)
│
├─ Observability & monitoring?
│ ├─ Metrics → Prometheus + Grafana
│ ├─ Distributed tracing → Jaeger or OpenTelemetry
│ ├─ Logs → Loki or ELK stack
│ ├─ eBPF-based → Cilium + Hubble (sidecarless)
│ └─ Unified platform → Datadog or New Relic
│
├─ Incident management?
│ ├─ On-call rotation → PagerDuty or Opsgenie
│ ├─ Postmortem → template-postmortem.md
│ └─ Communication → template-incident-comm.md
│
├─ Platform engineering?
│ ├─ Self-service → Backstage or Port (internal developer portal)
│ ├─ Policy enforcement → OPA/Gatekeeper
│ └─ Golden paths → Template repositories + automation
│
└─ Security hardening?
├─ Container scanning → Trivy or Grype
├─ Runtime security → Falco or Sysdig
├─ Secrets management → HashiCorp Vault or cloud-native KMS
└─ Compliance → CIS Benchmarks, template-security-hardening.md
Claude should invoke this skill when users request:
Operational best practices by domain:
Each guide includes:
Production templates organized by tech stack (27 templates total):
Resources
Shared Utilities (Centralized patterns — extract, don't duplicate)
Templates
Data
Operations & Infrastructure:
Security & Compliance:
Software Development:
AI/ML Operations:
See resources/operational-patterns.md for:
See data/sources.json for 45+ curated sources organized by tech stack:
Use this skill as a hub for safe, modern, and production-grade DevOps patterns. All templates and patterns are operational—no theory or book summaries.