Cross-Namespace Gateway and HTTPRoute Binding with Kubernetes Gateway API

Scenario

Your organization runs a railway platform with a strict separation between infrastructure and application teams. The infrastructure team owns the japan-railway-gateway namespace and manages all Gateway resources. The application team owns the japan-railway namespace where services run.

Two backend services are already running in the japan-railway namespace:

• schedule-service — serves train schedule data on port 3000
• ticket-service — serves ticket booking data on port 5000

Your goal is to expose both services externally through a single Gateway using path-based routing under the domain japan-railway.io.

Task

Create the required Kubernetes Gateway API resources across two namespaces:

• A Gateway named railway-gateway in namespace japan-railway-gateway that:
  • Listens on HTTP port 80
  • Uses gatewayClassName: nginx
  • Allows HTTPRoutes from the japan-railway namespace via allowedRoutes
• An HTTPRoute named railway-routes in namespace japan-railway that:
  • Attaches to railway-gateway in namespace japan-railway-gateway via parentRefs with namespace field set
  • Uses hostname japan-railway.io
  • Routes /schedule → schedule-service on port 3000
  • Routes /tickets → ticket-service on port 5000

Once the Gateway gets an external IP, verify that both routes respond correctly using japan-railway.io (/etc/hosts is already pre-configured on cplane-01).

curl http://japan-railway.io/schedule | jq

curl http://japan-railway.io/tickets | jq

Gateway in japan-railway-gateway namespace routing traffic to services in japan-railway namespace.

listeners:
- name: http
  port: 80
  protocol: HTTP
  allowedRoutes:
    namespaces:
      from: Selector
      selector:
        matchLabels:
          kubernetes.io/metadata.name: japan-railway

parentRefs:
- name: railway-gateway
  namespace: japan-railway-gateway

Test Cases