Skaffold
Skaffold — CLI tool for continuous K8s application development.
Stack Components
Why
Auto-rebuild and redeploy on file change, no manual kubectl apply during dev. Docker is used by 59% of professional developers per the Stack Overflow 2024 survey, and Terraform is used by 65% of organizations for IaC (HashiCorp 2024).
GitOps (ArgoCD, Flux) reduces deployment drift to near-zero by making git the single source of truth.
When
Use for K8s dev inner loop. Avoid for non-K8s workflows.
How
Example
Common Problems
- ⚠Sync not working — configure fileSync in skaffold.yaml
- ⚠Build failures — check builder (Docker/Jib/Bazel) config
- ⚠Configuration drift between environments — use infrastructure-as-code (Terraform/Pulumi) to keep dev/staging/prod identical
Best Practices
- ✓Use sync for faster dev iterations
- ✓Profile-based configs for dev/staging/prod
- ✓Set up health checks and graceful shutdown — handle SIGTERM to drain in-flight requests before exit
FAQ
What is Skaffold and what projects is it for?
Skaffold — CLI tool for continuous K8s application development. It pairs layered technologies for end-to-end type safety and out-of-the-box deploys, fitting everything from MVPs to production SaaS.
How do I spin up a working demo with Skaffold in 10 minutes?
Two steps: (1) Install skaffold; (2) Create skaffold.yaml. Get the local dev server running, then wire one real data source to verify the end-to-end loop.
What is the most common pitfall with Skaffold and how do I avoid it?
The most common pitfall is: Sync not working — configure fileSync in skaffold.yaml. Avoid it by adding the matching checklist to your PR template and running type-check + lint + unit tests in CI — three gates before merge.
What are the best practices for Skaffold?
Best practices for Skaffold include: Use sync for faster dev iterations; Profile-based configs for dev/staging/prod; Set up health checks and graceful shutdown — handle SIGTERM to drain in-flight requests before exit. The first one — "Use sync for faster dev iterations" — should be set up at project init to avoid costly rework later.
When should I NOT choose Skaffold?
Pick something else in three cases: (1) the team has zero experience with the core framework and the deadline is tight (learning-curve risk); (2) it's a pure content/marketing site (Astro is lighter); (3) you need very high throughput (>10k RPS) or strict-consistency microservices (Go/Rust). Skaffold shines for mid-to-high complexity full-stack and API work — don't over-engineer simple static pages with it.