If a Kubernetes cluster hosted on a public cloud provider fails to provision a requested load balancer service, which component might be responsible for this failure?

If a Kubernetes cluster hosted on a public cloud provider fails to provision a requested load balancer service, which component might be responsible for this failure?

• A. Scheduler
• B. The Cloud-Controller-Manager
• C. Kube-Proxy
• D. API Server

Answer: (B)

Cloud-specific resource provisioning for a LoadBalancer is handled by the cloud-controller-manager. When you create a service of type LoadBalancer, the cloud controller manager talks to the cloud provider to create an external load balancer and wires it to the Kubernetes service, updating the service with the external IP or hostname. If this integration fails—due to misconfig, missing or invalid cloud credentials, or cloud API errors—the load balancer won’t be provisioned. The other components don’t manage cloud resources: the scheduler places pods on nodes, Kube-proxy handles node networking, and the API Server serves and stores API data.

Cloud-specific resource provisioning for a LoadBalancer is handled by the cloud-controller-manager. When you create a service of type LoadBalancer, the cloud controller manager talks to the cloud provider to create an external load balancer and wires it to the Kubernetes service, updating the service with the external IP or hostname. If this integration fails—due to misconfig, missing or invalid cloud credentials, or cloud API errors—the load balancer won’t be provisioned. The other components don’t manage cloud resources: the scheduler places pods on nodes, Kube-proxy handles node networking, and the API Server serves and stores API data.