Demos and production are different sports. This checklist covers what changes when Kubernetes has to be reliable, secure and observable under real load.
Security and reliability defaults
- Enforce least privilege with RBAC and disable the default ServiceAccount token mount
- Apply NetworkPolicies to default-deny east-west traffic
- Run Pod Security Admission in 'restricted' mode and scan workloads with Trivy
A production-minded config
A Deployment plus Service with probes and resource limits.
apiVersion: apps/v1
kind: Deployment
metadata: { name: web }
spec:
replicas: 3
selector: { matchLabels: { app: web } }
template:
metadata: { labels: { app: web } }
spec:
containers:
- name: web
image: ghcr.io/acme/web:1.0
ports: [{ containerPort: 3000 }]
resources:
requests: { cpu: 100m, memory: 128Mi }
limits: { cpu: 500m, memory: 256Mi }
readinessProbe:
httpGet: { path: /healthz, port: 3000 }
---
apiVersion: v1
kind: Service
metadata: { name: web }
spec:
selector: { app: web }
ports: [{ port: 80, targetPort: 3000 }]Operational best practices
- Set requests/limits and use the HorizontalPodAutoscaler for elastic workloads
- Separate config (ConfigMap) from secrets and mount them, don't bake them in
- Use readiness probes to gate traffic and PodDisruptionBudgets for safe drains
- Adopt GitOps (ArgoCD/Flux) so the cluster state lives in reviewed Git
In production, boring and reproducible beats clever every time.
Want senior help putting Kubernetes to work - or a team bootcamp on it? CodeWizard runs Israel's largest DevOps community and embeds named senior engineers with a transparent hours log. Book a free consult or explore the Academy.