Kubernetes pods โ the smallest unit of deployment
A pod is not a container. Understanding the distinction โ and why Kubernetes uses pods as its fundamental unit โ is the first conceptual step to working effectively with Kubernetes.
I'm a technical evangelist writing and talking about Applied AI, Cloud-Native, and the future of India Tech โ with enough depth to be useful and enough clarity to be shareable.
What I write about
Each post, video, and experiment sits at the intersection of real-world engineering and where the industry is heading.
From local LLMs on cheap hardware to enterprise ML pipelines โ practical takes on building with AI, not just talking about it.
Containers, Kubernetes, CI/CD, and the engineering culture that makes modern infrastructure work. Starting from first principles.
Smart cities, semiconductor ambitions, startup ecosystems โ the India-specific angle that most global tech media misses entirely.
Deep dives, build logs, and opinion pieces โ published when there's something worth saying.
A pod is not a container. Understanding the distinction โ and why Kubernetes uses pods as its fundamental unit โ is the first conceptual step to working effectively with Kubernetes.
Once you have more containers than you can manage manually, you need an orchestrator. Kubernetes is the standard โ here's the architecture and the concepts you need to understand before running a single command.
Real applications aren't single containers. Here's how to build a Node.js + MongoDB two-container setup, wire them together over a custom network, and push the image to Docker Hub.
Docker creates three networks by default and lets you create more. Understanding which driver to use and when is what separates working setups from broken ones.
I work with early-stage teams and investors who need someone who can translate complex technology into clear decisions.