A county wants infrastructure operators to own the shared public entrypoint while application teams only attach their own HTTP routes. How should Gateway API ownership typically be split?
Select an answer to reveal the explanation.
Short Explanation
Picture the Gateway as the county’s shared lobby door that facilities owns, while each department posts its own directory signs (Routes) on that door. Ops keeps the entrypoint safe and stable; app teams attach only their HTTPRoute pieces.
Full Explanation
Gateway API encourages role separation: platform or cluster operators typically provision and secure Gateways (and GatewayClasses), while application teams create Routes that reference an allowed Gateway listener. That split reduces blast radius and keeps infrastructure ownership clear without forcing every team to run its own edge stack.