Pregunta de Container Orchestration #019e3a4f

The Kubernetes Control Plane is responsible for managing the cluster's state and making global decisions. Its core components include kube-apiserver, kube-scheduler, kube-controller-manager, and cloud-controller-manager. The cloud-controller-manager integrates with cloud provider APIs to manage resources like load balancers and storage volumes, making it a control plane component.

How it Works: The control plane components run on dedicated master nodes. kube-apiserver exposes the Kubernetes API, kube-scheduler assigns pods to nodes, kube-controller-manager runs controllers for replication, endpoints, etc., and cloud-controller-manager handles cloud-specific controllers. Together, they maintain the desired cluster state.

Why cloud-controller-manager is correct: It is explicitly listed as a control plane component in Kubernetes documentation. It manages cloud provider resources and runs as a controller within the control plane.

Why the other options are incorrect:

• coredns is a cluster add-on that provides DNS services for service discovery. It runs as a deployment on worker nodes, not as part of the control plane.
• kube-proxy is a network proxy that runs on each node (including worker nodes) to handle network rules and service load balancing. It is a node-level component, not a control plane component.
• kubelet is the primary node agent that runs on every node (including worker nodes) and ensures containers are running in pods. It is a node-level component, not part of the control plane.