terraform-k8slisted

Author and operate infrastructure-as-code with Terraform/OpenTofu and Kubernetes manifests — declarative provisioning, state management, modules, plan/apply discipline, and the K8s object model (Deployment/Service/Ingress, probes, requests/limits, HPA, ConfigMap/Secret, RBAC). Use when writing a Terraform module, structuring remote state and workspaces, debugging drift or a destructive plan, writing or reviewing K8s YAML/Helm/Kustomize, sizing requests/limits, or wiring probes. Boundary vs deployment-cicd — deployment-cicd owns the release process (CI pipeline, build/test stages, blue-green/canary/rolling rollout, version tagging, rollback playbook); this skill owns the substrate those releases deploy onto — declarative provisioning of cloud resources and the Kubernetes object definitions themselves. The pipeline runs apply; this skill is what those files contain. Defers image-build craft to docker and host-level tuning to linux-sysadmin.
kouroshez/coding-os · ★ 4 · DevOps & Infrastructure · score 76

Install: claude install-skill kouroshez/coding-os

# Terraform & Kubernetes — The Declarative Substrate A practical guide to provisioning cloud infrastructure with Terraform/OpenTofu and defining workloads as Kubernetes objects, such that the system state lives in version control and a fresh environment is one `apply` away. Stack-agnostic across cloud providers; recipes target AWS/GCP/Azure providers and vanilla K8s + Helm/Kustomize. ## When to Use This Skill - Writing or reviewing a Terraform/OpenTofu module — inputs, outputs, resource graph. - Structuring remote state, workspaces/environments, and state locking before a team touches it. - Reading a `terraform plan` that wants to destroy/recreate something and deciding if that is safe. - Authoring K8s manifests (Deployment, Service, Ingress) or a Helm chart / Kustomize overlay. - Sizing resource requests/limits, wiring liveness/readiness/startup probes, configuring an HPA. - Managing config and secrets (ConfigMap, Secret, external secret operators) and RBAC. Skip when: the question is *how releases ship* (pipeline stages, rollout strategy, versioning, rollback) — that is deployment-cicd. This skill is the infrastructure those releases land on. ## Terraform — State Is the Whole Game Terraform's model: a `.tf` description of desired state, a state file recording what actually exists, and `plan`/`apply` reconciling the two. Everything hard about Terraform is about state. - **Remote, locked state from day one.** Never a local `terraform.tfstate` for shared infra — two `ap