Kubernetes, Explained Without the Hype

What Kubernetes actually does (keeps your declared desired state true across many machines), the handful of objects you really meet - Pod, Deployment, Service, controllers - and a straight answer to whether you need it at all.

1. The Problem K8s Solves Running many containers across many machines by hand is brutal - placement, restarts, scaling, networking, rollouts. Kubernetes is a container orchestrator: you declare the desired state and it works continuously to make reality match.
2. The Core Objects The pieces you actually meet: the Pod (one or more containers), the Deployment (desired replicas + safe rollouts), the Service (a stable address + load balancing), and the controllers that reconcile actual toward desired - shown with annotated YAML and kubectl transcripts.
3. Should You Even Use It? The straight cost-benefit: Kubernetes is powerful and genuinely complex, and the operational cost is real. Most small apps are happier on a VPS or a PaaS. When k8s actually earns its keep - real scale, many services, a platform team - and how to dodge resume-driven Kubernetes.