A city platform team wants one shared north-south HTTP entrypoint that can host many municipal host and path routes with portable, role-friendly resources. Which Kubernetes approach best matches that goal?
Select an answer to reveal the explanation.
Short Explanation
Think of Gateway API as the city’s shared front desk: one doorway (Gateway) and labeled routes for each department’s apps. It is built for hosting lots of HTTP host and path rules in a cleaner, more portable way than annotation-heavy Ingress spaghetti.
Full Explanation
Gateway API models north-south HTTP(S) traffic with Gateway and Route resources that attach to listeners. Municipal platforms use it to centralize entry while keeping routing declarative and portable across implementations. ClusterIP Services still front pods; Gateway API does not replace in-cluster service discovery or CoreDNS.