KCNA · Question #9
Scenario: You have a Kubernetes cluster hosted in a public cloud provider. When trying to create a Service of type LoadBalancer, the external-ip is stuck in the "Pending" state. Which Kubernetes compo
The correct answer is A. Cloud Controller Manager. When a LoadBalancer Service's external-IP is stuck in "Pending" in a public cloud, it indicates a failure in the Cloud Controller Manager, which is responsible for provisioning cloud infrastructure.
Question
Scenario: You have a Kubernetes cluster hosted in a public cloud provider. When trying to create a Service of type LoadBalancer, the external-ip is stuck in the "Pending" state. Which Kubernetes component is failing in this scenario?
Options
- ACloud Controller Manager
- BLoad Balancer Manager
- CLoad Balancer Manager
- DCloud Load Balancer Manager
How the community answered
(26 responses)- A88% (23)
- B8% (2)
- D4% (1)
Why each option
When a LoadBalancer Service's external-IP is stuck in "Pending" in a public cloud, it indicates a failure in the Cloud Controller Manager, which is responsible for provisioning cloud infrastructure.
The Cloud Controller Manager is a Kubernetes control plane component responsible for interacting with the underlying cloud provider's APIs. For a Service of type LoadBalancer, it is the Cloud Controller Manager's job to provision an external load balancer on the cloud provider, and if it's stuck in "Pending," it signals a failure in this component or its communication with the cloud API.
"Load Balancer Manager" is not a standard Kubernetes component.
"Load Balancer Manager" is not a standard Kubernetes component.
"Cloud Load Balancer Manager" is not a standard Kubernetes component; the correct component is the Cloud Controller Manager.
Concept tested: Cloud Controller Manager role in Service LoadBalancer provisioning
Source: https://kubernetes.io/docs/concepts/architecture/cloud-controller/
Topics
Community Discussion
No community discussion yet for this question.