An HR LoadBalancer Service remains External IP Pending in a bare-metal lab with no cloud load-balancer controller. What explains the stuck state?
Select an answer to reveal the explanation.
Short Explanation
LoadBalancer is a request for a real front-door IP from a provider—no cloud or MetalLB-style controller, no address, forever Pending. Lab clusters need a provider or a different Service type.
Full Explanation
type: LoadBalancer waits for an implementation to allocate EXTERNAL-IP. Bare-metal clusters without MetalLB/cloud integration remain Pending. restartPolicy, CoreDNS NodePort myths, and Ingress count do not allocate that address.