Please enable JavaScript.

Coggle requires JavaScript to display documents.

KUBERNETES, Recommended lecture - Coggle Diagram

- - - - Each Node runs the software necessary to host Pods:
      - kubelet → talks to the API server, ensures containers are running.
      - container runtime → e.g., Docker, containerd (runs the actual containers).
      - kube-proxy → handles networking/routing for Pods on the node.
  - - - Containers in a Pod:
        
        Share the same network namespace (same IP address, can talk to each other via localhost).
        
        Can share storage volumes.
        
        Are scheduled together.
  - - - Common use cases:
        
        Separate environments (e.g., dev, test, prod).
        
        Separate teams or projects in a shared cluster.
        
        Apply different resource limits and access controls.
  - - - Kubernetes uses it as the backing database to store the entire cluster state.
  - - - Its primary function is to determine which Node a Pod should run on, ensuring efficient resource utilization and adherence to specified constraints.
  - - - Its main job: make sure the containers that are supposed to run on that node are actually running.
        It constantly talks with the API server and the container runtime (like containerd or Docker).
        
        The scheduler assigns a Pod to a worker node.
        
        The API server tells kubelet on that node: “Run this Pod with these containers.”
        
        The kubelet:
        
        Talks to the container runtime (containerd/Docker) to start the containers.
        
        Mounts volumes if needed.
        
        Sets up networking (via CNI plugins).
        
        The kubelet reports back to the control plane:
        
        Pod is Running, Pending, or Failed.
        
        Sends resource usage and health info.