Topic
Kubernetes is a control loop: you declare the state you want, and controllers work continuously to make the cluster match it. Almost everything that feels confusing at first — why a pod came back after you deleted it, why a rollout stalled — follows from that one idea.
The gap between a working cluster and a well-run one is mostly resource limits, probes and rollout strategy. Those three decide whether a bad deploy degrades one pod or takes down the service.
Existing pages in an order where each step answers a question the previous one raised, with an exercise at the end.
Step-by-step, with copy-paste commands and an assistant that answers questions about the guide you are reading.
Named errors and symptoms, each with its causes, a command that confirms each one, and the fix.
OOMKilled is the signature, and the question is whether the limit is too low, the application is leaking, a spike hit, or the node was overcommitted.Pairs of things that get mistaken for one another, and the problem the mix-up causes.
The design decision behind the behaviour, and what it costs you.
A failure followed step by step: what each part of the system does, and what you can change.
limits.memory is a hard limit, enforced by the OOM killer rather than by slowing the process down.Run in your browser; nothing you paste is sent anywhere.
A question, then the follow-ups an interviewer asks when the first answer is right.
Ordered by how much they are read.
Kubernetes explained through the control loop under Pods, Deployments and Services, so you can predict what the cluster will do, not just name its parts. Most introductions stop at the nouns.
Neeraj Jha
Updated
Learn GitOps principles and implement them with ArgoCD — automated Kubernetes deployments driven by Git pull requests.
Neeraj Jha
How to get oriented in a Kubernetes YAML file you did not write: four hundred lines, in production, by somebody who left. An order that works, and why the file may not be what is running.
Neeraj Jha
Updated
Deep dive into Kubernetes networking — ClusterIP, NodePort, LoadBalancer, Ingress controllers, CoreDNS, and Network Policies explained with examples.
Neeraj Jha
Updated
What actually changes moving from DevOps to platform engineering: your work stops being mandatory and starts being optional, and every design decision is now a negotiation with somebody's convenience.
Neeraj Jha
Master Helm charts for Kubernetes — chart structure, values, templates, repositories, environment management, and deployment best practices.
Neeraj Jha
Updated
Why a Kubernetes cluster is full at 10% utilisation: the scheduler commits against requests, not usage, and that gap is where most overspend lives. Your dashboards and the scheduler are both right.
Neeraj Jha
Ingress NGINX was retired in March 2026, and moving the same rules to Gateway API can break routes that worked for years. Five behaviours from the Kubernetes project's own write-up, in plain language, with a check to run before you switch.
Neeraj Jha
CrashLoopBackOff means a Kubernetes container keeps exiting and being restarted. Read the previous container's logs, its exit reason and the pod events, and the cause is usually on screen.
Neeraj Jha
OOMKilled means the kernel killed a Kubernetes container for using too much memory. How to tell a low limit from a leak or a one-off spike before you raise anything.
Neeraj Jha
Real questions from the community, with an accepted answer.