🖼️ Page 1: Kubernetes Core Components Map (Replace Image in Graphy Page Builder)

1. Pods — Smallest Deployable Units

A Pod is the foundational execution unit in Kubernetes. It represents a single instance of a running process in your cluster and wraps one or more containers that share network, storage, and lifecycle specifications.

🖼️ Page 2: Pod Architecture, Shared IP/Storage & Lifecycle (Replace Image in Graphy)

2. Nodes — The Workhorses of Kubernetes

A Node is a worker machine (virtual machine or physical bare-metal server) where containerized Pod workloads are scheduled and run.

🖼️ Page 3: Node Architecture (Control Plane vs Worker Nodes) (Replace Image in Graphy)

Essential Node Components:

• kubelet — Primary node agent that communicates with API Server and enforces container state inside Pods.
• kube-proxy — Network proxy maintaining network rules on nodes and enabling Service connectivity across the cluster.
• Container Runtime — Underlying software that executes containers (e.g. containerd, CRI-O, Docker).

3. Deployments — Declarative Application Scaling

A Deployment provides declarative updates for Pods and ReplicaSets. You describe a desired state in a Deployment YAML, and the Deployment Controller transitions the actual state to the desired state at a controlled rate.

🖼️ Page 4: Deployments, ReplicaSets & Rolling Update Flow (Replace Image in Graphy)

apiVersion: apps/v1
kind: Deployment
metadata:
  name: nginx-deployment
spec:
  replicas: 3
  selector:
    matchLabels:
      app: nginx
  template:
    metadata:
      labels:
        app: nginx
    spec:
      containers:
      - name: nginx
        image: nginx:1.25
        ports:
        - containerPort: 80

4. Services — Stable Networking for Pods

Pods are ephemeral and get dynamic IP addresses assigned upon restart. A Service is an abstraction that defines a logical set of Pods and a policy to access them, providing a persistent Virtual IP (VIP) and DNS name.

🖼️ Page 5: Service Types (ClusterIP, NodePort, LoadBalancer) (Replace Image in Graphy)

5. Ingress — Smart HTTP/HTTPS Routing

Ingress manages external HTTP and HTTPS access to services within a cluster. It supports path-based and host-based routing, SSL/TLS termination, and centralized load balancing under a single IP address.

🖼️ Page 6: Ingress Controller Host & Path-Based Routing (Replace Image in Graphy)

apiVersion: networking.k8s.io/v1
kind: Ingress
metadata:
  name: example-ingress
spec:
  rules:
  - host: example.com
    http:
      paths:
      - path: /app1
        pathType: Prefix
        backend:
          service:
            name: service-a
            port:
              number: 80
      - path: /app2
        pathType: Prefix
        backend:
          service:
            name: service-b
            port:
              number: 80

6. ConfigMaps & Secrets — Configuration Management

Decoupling configuration artifacts from application code makes containerized workloads portable across environments (Dev, Staging, Prod).

🖼️ Page 7: ConfigMaps Non-Sensitive Data Storage (Replace Image in Graphy)

🖼️ Page 8: Secrets Encrypted Sensitive Data Storage (Replace Image in Graphy)

7. Storage — Persistent Storage for Stateful Workloads

Kubernetes separates storage requests from storage implementation using three abstractions:

• PersistentVolume (PV): A cluster-wide storage resource provisioned by admins or dynamically created by StorageClass.
• PersistentVolumeClaim (PVC): A request for storage by a user/Pod (specifying size and access mode).
• StorageClass (SC): Defines dynamic provisioners (AWS EBS, GCP PD, NFS) and storage parameters.

🖼️ Page 9: Persistent Storage Architecture (PV, PVC, StorageClass) (Replace Image in Graphy)

8. Networking Architecture (CNI, Kube-Proxy & CoreDNS)

Kubernetes networking enforces the fundamental rule: Every Pod receives its own unique IP address and can communicate with all other Pods without NAT.

🖼️ Page 10: CNI Networking, Kube-Proxy Routing & CoreDNS Flow (Replace Image in Graphy)

9. Pod Scheduling, Taints & Affinity

The kube-scheduler assigns unscheduled Pods to optimal Worker Nodes based on resource requests, constraints, and affinity rules.

🖼️ Page 11: Scheduler Flow, Taints, Tolerations & Affinity (Replace Image in Graphy)

10. Kubernetes Architecture & CLI Command Cheat Sheet

🖼️ Page 12: Kubernetes Master Architecture & CLI Cheat Sheet (Replace Image in Graphy)