| name | infra-release-readiness |
| description | PetSwipe infrastructure and deployment workflow for Kubernetes, Terraform, production Docker Compose, release bundle, and preflight validation. Use when the task is explicitly about deployability, production readiness, operator workflow, or infra/devops changes. |
Use this skill for deployment-readiness and infra/devops work in PetSwipe.
Workflow
- Inspect the touched infra area first: Kubernetes, Terraform, Docker Compose, scripts, or docs.
- Run the strongest repo-native validation available.
- Separate what is repo-ready from what still depends on real operator values.
- Update operator docs when the workflow changes.
- Do not claim enterprise readiness unless the repo and operator prerequisites both support it.
Repo-Specific Guidance
- Kubernetes validation lives in
make k8s-preflight, make k8s-render, and make k8s-render-prod.
- Terraform validation starts with
make tf-preflight ENV=production.
- Deploy and release guardrails exist in:
scripts/deploy-preflight.shscripts/terraform-preflight.shscripts/k8s-preflight.shscripts/release-bundle.sh
- Production still depends on real operator inputs like
.env.production, terraform/backend.hcl, terraform/environments/*.tfvars, and non-placeholder Kubernetes values.
Read references/deployment-checklist.md before concluding.
