Which statement about the Cloud-Controller-Manager is NOT accurate?

Which statement about the Cloud-Controller-Manager is NOT accurate?

• A. It bridges cloud provider functionality to Kubernetes
• B. It manages cloud-specific resources like load balancers and instances
• C. It handles DNS for Services
• D. It synchronizes cloud resources with the cluster state

Answer: (C)

The Cloud Controller Manager runs cloud-specific control loops that connect Kubernetes with the cloud provider. It acts as a bridge, allowing Kubernetes to request and manage cloud resources—like provisioning or tearing down load balancers and VM instances—so the cluster’s desired state is reflected in the cloud. It also keeps cloud resources in sync with the cluster state, such as ensuring the cloud’s view of instances and networking matches the nodes and services defined in Kubernetes. DNS for Services isn’t handled by this component. DNS for Services is provided by the cluster’s DNS add-on (such as CoreDNS or kube-dns), which creates and resolves the in-cluster service names. The Cloud Controller Manager does not manage DNS records for Services.

The Cloud Controller Manager runs cloud-specific control loops that connect Kubernetes with the cloud provider. It acts as a bridge, allowing Kubernetes to request and manage cloud resources—like provisioning or tearing down load balancers and VM instances—so the cluster’s desired state is reflected in the cloud. It also keeps cloud resources in sync with the cluster state, such as ensuring the cloud’s view of instances and networking matches the nodes and services defined in Kubernetes.

DNS for Services isn’t handled by this component. DNS for Services is provided by the cluster’s DNS add-on (such as CoreDNS or kube-dns), which creates and resolves the in-cluster service names. The Cloud Controller Manager does not manage DNS records for Services.