, this summary provides a comprehensive look at those and other industry-standard principles. Amazon.com I. Core Architectural Components Control Plane : The orchestration layer that manages the cluster state. Worker Node

Determines if a container needs to be restarted. If it fails, Kubernetes kills the container and initiates its restart policy. 46. Readiness Probe

The safety net. It ensures that a specified number of identical pod replicas are running at any given time. 14. Deployment

The software responsible for running containers. Kubernetes supports runtimes like containerd and CRI-O. Part 2: Workloads & Pod Orchestration

: A virtual cluster abstraction used to isolate groups of resources within a single physical cluster.

: Checks if a container is running and ready to serve traffic. Custom Resource Definition (CRD) : Extends Kubernetes by creating your own object types. DEV Community Suggested Free Resources: Packt Publishing (GitHub Repo)

A consistent, highly available key-value store. It holds all configuration data and the state of your cluster. 5. Controller Manager (kube-controller-manager)

: The software responsible for running containers (e.g., containerd, CRI-O). II. Workloads and Objects 50 Kubernetes Concepts Every DevOps Engineer ... - GitHub

Ensures that a pod runs on every node in the cluster (or a subset of nodes). Common use cases include log collection (Fluentd), monitoring (Prometheus Node Exporter), and networking components (Calico).