On a cloud Kubernetes cluster, a public parks website should get a provider-provisioned external address in front of its Service. Which type requests that?
Select an answer to reveal the explanation.
Short Explanation
LoadBalancer is the “please give me a cloud front door” Service type. On a supported provider, the cloud controller hangs an external LB (and usually an address) on that Service. ClusterIP and headless won’t summon that managed front end by themselves.
Full Explanation
Service type LoadBalancer asks the cloud provider’s integration to provision an external load balancer targeting the Service’s backends. ClusterIP remains internal; headless Services are for direct Pod DNS discovery; NodePort alone does not create a managed cloud load balancer though LoadBalancer implementations often build on node ports underneath.