In a managed Kubernetes service, which component handles cloud provider integration for resources like LoadBalancer?

In a managed Kubernetes service, which component handles cloud provider integration for resources like LoadBalancer?

• A. Cluster Autoscaler
• B. Cloud Controller Manager
• C. Kube Proxy
• D. CoreDNS

Answer: (B)

The Cloud Controller Manager handles cloud provider integration for resources like LoadBalancer. It runs cloud-specific controllers that talk to the cloud provider’s API to provision and manage external resources such as load balancers, routes, and other cloud resources, keeping the Kubernetes control plane itself cloud-agnostic. When you create a Service of type LoadBalancer, the Cloud Controller Manager provisions the external load balancer in the cloud and connects it to the service. Other components serve different roles: Kube Proxy manages in-cluster networking for services, CoreDNS provides DNS for service discovery, and the Cluster Autoscaler adjusts the number of nodes.

The Cloud Controller Manager handles cloud provider integration for resources like LoadBalancer. It runs cloud-specific controllers that talk to the cloud provider’s API to provision and manage external resources such as load balancers, routes, and other cloud resources, keeping the Kubernetes control plane itself cloud-agnostic. When you create a Service of type LoadBalancer, the Cloud Controller Manager provisions the external load balancer in the cloud and connects it to the service.

Other components serve different roles: Kube Proxy manages in-cluster networking for services, CoreDNS provides DNS for service discovery, and the Cluster Autoscaler adjusts the number of nodes.