Control Plane Components:

• API Server: The front-end for the Kubernetes control plane, handling all REST operations
• etcd: Distributed key-value store for all cluster data
• Scheduler: Assigns pods to nodes based on resource requirements and constraints
• Controller Manager: Runs controller processes that regulate cluster state
• Cloud Controller Manager: Integrates with cloud provider APIs (like Azure in your case)

Node Components:

• kubelet: Agent running on each node that ensures containers are running in pods
• kube-proxy: Network proxy maintaining network rules for pod communication
• Container Runtime: Software responsible for running containers (containerd, CRI-O, etc.)

Core Abstractions:

• Pod: Smallest deployable unit, contains one or more containers
• Service: Stable endpoint for accessing pods (ClusterIP, NodePort, LoadBalancer)
• Deployment: Declarative way to manage pod replicas and updates
• StatefulSet: For stateful applications requiring persistent identities
• DaemonSet: Ensures a pod runs on all (or specific) nodes
• ConfigMap/Secret: Configuration and sensitive data management
• Namespace: Virtual clusters for resource isolation

Service Discovery & Load Balancing: Kubernetes can expose containers using DNS names or IP addresses and distribute traffic across pods.

Storage Orchestration: Automatically mounts storage systems (local, cloud providers like Azure Blob/File, network storage). In your infrastructure, you use Azure storage classes (azureblob, azurefile, managed disks).

Automated Rollouts & Rollbacks: Gradually rolls out changes to applications, monitors health, and can automatically rollback if issues occur.

Self-Healing: Restarts failed containers, replaces and reschedules pods when nodes die, kills containers that don't respond to health checks.

Secret & Configuration Management: Manages sensitive information and configuration without rebuilding container images. Your infrastructure integrates with [OMITTED]

Horizontal Scaling: Automatically scales applications based on CPU usage, memory, or custom metrics.

Batch Execution: Manages batch and CI workloads alongside long-running services.

Based on your repository context, you're using Kubernetes with:

[OMITTED]

Portability: Run anywhere - on-premises, public cloud, hybrid environments.

Declarative Configuration: Define desired state, Kubernetes ensures actual state matches.

Extensibility: Rich ecosystem of tools and extensions (service meshes, monitoring, CI/CD).

Resource Efficiency: Better utilization through bin-packing and auto-scaling.

High Availability: Built-in fault tolerance and self-healing capabilities.

Vendor Neutrality: Open-source with strong community and multi-cloud support.

DevOps Enablement: Facilitates continuous deployment, infrastructure-as-code, and GitOps workflows.

[OMITTED]