When Kubernetes misbehaves, the cause is usually one of a handful of familiar issues. Here is how to spot and fix them fast.
The usual suspects
- No resource requests/limits - the scheduler can't pack pods and OOM kills surprise you
- Using :latest images so rollbacks and caching become unpredictable
- Liveness probes that are too aggressive, restarting healthy-but-slow pods
- Treating Secrets as encrypted - they are only base64-encoded at rest by default
Commands for diagnosis
kubectl apply -f deploy.yaml
kubectl rollout status deploy/web
kubectl get pods -l app=web
kubectl logs deploy/web
kubectl rollout undo deploy/web # roll back the last changePrevent the repeat
- 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
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.