An open-data portal Service listens on port 80 for clients but cont…

Question

An open-data portal Service listens on port 80 for clients but containers listen on port 8080. How should the Service map those ports?

Accepted Answer

Set service port to 80 and targetPort to 8080 so clients use the stable Service port while traffic hits the container port. — Clients dial extension 80; the app's desk is 8080 — port is the directory number, targetPort is the real desk.

Answer

Set both port and targetPort to 80 and rename the container port field to servicePort.

Answer

Use nodePort 8080 with targetPort 80 so in-cluster ClusterIP traffic remaps automatically.

Answer

Put 8080 only in the Service name metadata; kube-proxy infers targetPort from the name.

An open-data portal Service listens on port 80 for clients but containers listen on port 8080. How should the Service map those ports?

Short Explanation

Full Explanation