Is it possible to set a timeout for each client in service mesh communication using HTTPRoute?

[S-mishina]

Thank you for creating a great mechanism!

In the future, I am planning to switch from istio api to gateway api and design Service Mesh communication.
In the process, I'm faced with the challenge of designing an appropriate timeout for each application that uses the gateway api.
What I want to achieve is this image.

I used the gateway api and found that if I set HTTPRoute for each namespace, I could set the timeout for each namespace.

Example)

apiVersion: v1
kind: Namespace
metadata:
  name: test
  labels:
    istio-injection: enabled
---
apiVersion: v1
kind: Namespace
metadata:
  name: test1
  labels:
    istio-injection: enabled
---
apiVersion: apps/v1
kind: Deployment
metadata:
  name: b-service-deployment
spec:
  replicas: 1
  selector:
    matchLabels:
      app: flexiblemockserver
  template:
    metadata:
      labels:
        app: flexiblemockserver
    spec:
      containers:
      - name: mock
        image: ghcr.io/s-mishina/flexiblemockserver
        ports:
        - containerPort: 8080
---
apiVersion: apps/v1
kind: Deployment
metadata:
  name: a-service-deployment
  namespace: test
spec:
  replicas: 1
  selector:
    matchLabels:
      app: nginx
  template:
    metadata:
      labels:
        app: nginx
    spec:
      containers:
      - name: nginx
        image: nginx:latest
        ports:
        - containerPort: 80
---
apiVersion: apps/v1
kind: Deployment
metadata:
  name: c-service-deployment
  namespace: test1
spec:
  replicas: 1
  selector:
    matchLabels:
      app: nginx
  template:
    metadata:
      labels:
        app: nginx
    spec:
      containers:
      - name: nginx
        image: nginx:latest
        ports:
        - containerPort: 80
---
apiVersion: v1
kind: Service
metadata:
  name: mock-service
spec:
  selector:
    app: flexiblemockserver
  ports:
    - protocol: TCP
      port: 8080
      targetPort: 8080
  type: ClusterIP
---
apiVersion: gateway.networking.k8s.io/v1beta1
kind: HTTPRoute
metadata:
  name: mesh
  namespace: test1
spec:
  parentRefs:
  - group: ""
    kind: Service
    name: mock-service
    namespace: default
  rules:
  - backendRefs:
    - name: mock-service
      namespace: default
      port: 8080
    timeouts:
      request: 2s

This approach would certainly allow flexibility in changing timeouts on a per-namespace basis, but in a controller management environment that includes a mechanism to control HTTPRoute (e.g., a custom controller for progressive delivery), I don't think this is feasible.

So I tried to find out if it is possible to apply the configuration to a specific pod, like the sourceLabels method of istio api (virtualservice), but it does not seem to be possible.
It did not seem to be possible with HTTPRoute alone.

Is it possible to use the current gateway api HTTPRoute to achieve what you wrote above?
If not, do you plan to support it?

Sorry if I am going about this the wrong way!
I'd love to know a good way to do it.

Finally, thanks for reading my long post.
Please answer me.

[S-mishina]

This question should have been asked in the istio community.