Relationship Diagram (with 1→N associations) What “one-to-many” means here (plain English) 1) Physical Machine → VMs (1→N) A single physical server can host many VMs (depending on CPU/RAM limits). Why? Virtualization slices hardware into multiple isolated “computers”. 2) Node → Pods (1→N) A node (a worker machine) typically runs many pods. Why? Kubernetes schedules pods […]
Below is a clear mental model for how container, pod, node, VM, and physical machine relate. Think of them as layers of “where software runs”, from hardware up to your app process. The “stack” in one picture (most common in cloud Kubernetes) In short:\ Physical machine → (Hypervisor) → VM → Node → Pod → […]
Big Picture Overview Modern systems don’t run on “just code.” They run on infrastructure: networks, databases, load balancers, Kubernetes clusters, IAM roles, message queues, and more. In the cloud, these are all created through APIs—meaning your infrastructure is effectively software-controlled. But there’s a catch: Terraform exists to solve this. Terraform is a tool for Infrastructure […]
Introduction Kubernetes is one of the most in-demand technologies in the software industry today, with 96% of organizations either using or evaluating it. However, many developers struggle when learning Kubernetes not because Kubernetes is inherently difficult, but because they lack foundational knowledge in prerequisite concepts. This tutorial explains all the core terminologies and concepts you […]
My Notes 