Sanitation must publish several citizen HTTP apps with host- and pa…

Question

Sanitation must publish several citizen HTTP apps with host- and path-based routing on a shared entrypoint. When is Gateway API a better fit than exposing each app with only a raw NodePort?

Accepted Answer

When you need L7 HTTP host/path routing and shared edge features instead of simple per-Service L4 node ports — NodePort is a plain numbered side door on every node. Gateway API is the shared lobby with host and path signs—use it when citizens need proper HTTP routing, not just a raw high port.

Answer

When Pods must avoid Services entirely and bind host ports on every worker

Answer

When the only requirement is east-west ClusterIP traffic inside one namespace

Answer

When CoreDNS is unavailable and NodePort numbers should replace all DNS names

Sanitation must publish several citizen HTTP apps with host- and path-based routing on a shared entrypoint. When is Gateway API a better fit than exposing each app with only a raw NodePort?

Short Explanation

Full Explanation