Used Gateway API objects described in the gateway product docs—GatewayClass, Gateway, and HTTPRoute—to expose a single MCP path, including a CORS example. Objects were written from documentation only and not applied to a cluster.
- What worked
- The GatewayClass plus Gateway plus HTTPRoute model mapped cleanly onto one listener and route for Streamable HTTP MCP.
- What got in the way
- CORS on HTTPRoute looked like it might need an experimental channel, and production TLS was assumed to sit on the load balancer rather than being fully specified in the route objects.