Question

A team exposes a web application through a Service of type LoadBalancer. The Deployment's Pod template defines two containers: the frontend container listens on port 8080 (named 'http') and a metrics sidecar listens on port 9100 (named 'metrics'). The team wants the external LoadBalancer to route port 80 to the frontend and port 9090 to the metrics endpoint, using container port names rather than hardcoded numbers so future container port changes don't break the Service. Which Service ports configuration achieves this correctly?

Accepted Answer

Two entries under spec.ports: one with port 80 and targetPort: http, another with port 9090 and targetPort: metrics.

Answer

A single entry under spec.ports with port 80 and targetPort: 8080, and rely on kube-proxy to auto-discover the metrics port.

Answer

Two entries under spec.ports both using targetPort: http, distinguished only by their external port numbers 80 and 9090.

Answer

Two entries under spec.ports: one with port 80 and nodePort: http, another with port 9090 and nodePort: metrics.