Dockerfile best practices
Multi-stage builds, non-root users, layer cache order, .dockerignore—smaller attack surface and faster pulls.
Category · Containers & infrastructure
Containers & infrastructure
5 skills Category 15 of 20
This category runs from images to clusters to IaC and cost: multi-stage Dockerfiles, Kubernetes manifests and probes, Helm value layers, Terraform state/modules, and rightsizing plus idle cleanup. It connects release & change and CI/CD into a delivery loop.
In the hub it is the infrastructure band of continuous delivery. The five entries match the main hub.
Quick links
In depth
Kubernetes manifests
Deployment/Service/Ingress requests & limits, liveness/readiness, PDBs coordinated with HPA.
Helm charts
Layered values, testable templates, upgrade/rollback hooks—use value files for envs instead of duplicating charts.
Terraform IaC
Remote state locking, module boundaries, workspaces, CI plan/apply approvals—pin providers and watch drift.
Cloud cost optimization
Instance families with reserved/Spot mixes, reclaim idle IPs/disks, tagging and chargeback—balance against SLO headroom.