Write Kubernetes Manifests from a Plain-English Description
Kubernetes manifests are full of boilerplate that's easy to get subtly wrong — label selectors that don't match, readiness probes with the wrong timing, missing resource limits. Describe what you need and let Claude handle the YAML.
Write Kubernetes manifests for a Node.js API service:
- Deployment with 3 replicas, rolling update strategy
- Image: my-registry/api:latest, port 3000
- Resource limits: 512Mi memory, 500m CPU
- Readiness probe on GET /health with a 5s initial delay
- ClusterIP Service exposing port 80 → container port 3000
- ConfigMap for non-secret environment variables
Claude will produce well-structured YAML with proper labels, selector consistency, and sensible defaults — the kind of boilerplate that's easy to get slightly wrong by hand.
spec:
replicas: 3
strategy:
type: RollingUpdate
template:
spec:
containers:
- name: api
resources:
limits:
memory: "512Mi"
cpu: "500m"
readinessProbe:
httpGet:
path: /health
port: 3000
initialDelaySeconds: 5
Ask it to add a HorizontalPodAutoscaler, Ingress, or NetworkPolicy as follow-up requests — each one builds on the labels and names already defined, so Claude keeps everything consistent.
Describing intent in plain English and letting Claude handle the YAML syntax beats the Kubernetes docs every time.
Log in to leave a comment.
Set up Claude Code as an automated reviewer in your CI pipeline — on every pull request, it reads the diff, checks for bugs, security issues, missing tests, and convention violations, then posts its findings as a PR comment. Your human reviewers get a head start because the obvious issues are already flagged before they look.
Before deploying, tell Claude to read your project — migrations, environment variables, queue workers, scheduled tasks, caching, third-party integrations — and generate a deployment checklist that's specific to your app. Not a generic "did you run migrations?" list, but one that knows YOUR infrastructure and catches the things YOUR deploy can break.
Instead of writing a README from memory or copying a template, tell Claude to read your project and generate one that's actually accurate — real setup instructions from your config, real architecture from your directory structure, real API examples from your routes, and real prerequisites from your dependency files.