Which approach exposes an internal-only HTTP service to other resources in the VNet without a public IP?
- A Service type LoadBalancer with the azure-load-balancer-internal annotation (correct answer)
- B Service type NodePort
- C Ingress with a public IP
- D Service type ExternalName
Shortcut: io/azure-load-balancer-internal: "true" provisions an internal Azure Load Balancer reachable only from the VNet.
Annotating a LoadBalancer Service with service.beta.kubernetes.io/azure-load-balancer-internal: "true" provisions an internal Azure Load Balancer reachable only from the VNet.