HTTPRouteFilter direct response does not work

[ovaldi]

EG version: v1.2.4
K8s version: v1.31

[arkodg]

you shouldnt be specifying a backendRef for this case, and if you do, it should be a valid one (still will have no effect and directResponse will kick in), if Envoy Gateway finds any invalid config (non existent backend maps to invalid config), if adds a directResponse of 500, closing this one since it working as designed, feel free to reopen if you have futher questions

[ovaldi]

you shouldnt be specifying a backendRef for this case, and if you do, it should be a valid one (still will have no effect and directResponse will kick in), if Envoy Gateway finds any invalid config (non existent backend maps to invalid config), if adds a directResponse of 500, closing this one since it working as designed, feel free to reopen if you have futher questions

@arkodg I think there is misunderstood, the backendRef in the picture belongs to another rule, and the backendRef is valid. (maybe K9s' screenshot misled you)
What I need is that all OPTIONS requests return 200 directly, and other requests are handled by backendRef.

[arkodg]

ah my bad, but I dont see that error in the test cases
input: https://github.com/envoyproxy/gateway/blob/main/internal/gatewayapi/testdata/httproute-with-direct-response.in.yaml
output: https://github.com/envoyproxy/gateway/blob/main/internal/gatewayapi/testdata/httproute-with-direct-response.out.yaml

[ovaldi]

I tried many times and check the code, didn't find a solution.

[arkodg]

@ovaldi do you have multiple routes referencing the same filter ? you maybe hitting #4989

[ovaldi]

@ovaldi do you have multiple routes referencing the same filter ? you maybe hitting #4989

@arkodg I have multiple routes but only one filter eg-cors-filter and only one route references it.

[guydc]

@ovaldi - it seems like the HTTPRouteFilter has no namespace, so it's probably applied in the default namespace in your cluster. The filter should be in the same namespace as your route, which is in envoy-gateway-system.

[ovaldi]

@ovaldi - it seems like the HTTPRouteFilter has no namespace, so it's probably applied in the default namespace in your cluster. The filter should be in the same namespace as your route, which is in envoy-gateway-system.

Hi @guydc I double-checked that the HTTPRouteFilter exists in the same namespace.
We use helm chart to deploy & upgrade gateway templates and specify namespace -n envoy-gateway-system

[guydc]

Thanks @ovaldi.

Can you please provide a more standalone step-by-step reproduction of the issue? e.g. install Envoy Gateway version X with Y helm values and apply resources Z (Gateway, Route, Filters in a yaml format [not picture])?

[ovaldi]

Thanks @ovaldi.

Can you please provide a more standalone step-by-step reproduction of the issue? e.g. install Envoy Gateway version X with Y helm values and apply resources Z (Gateway, Route, Filters in a yaml format [not picture])?

We were previously using EG v1.1.1 and recently upgraded to v1.2.4

helm install eg oci://docker.io/envoyproxy/gateway-helm \
  --version v1.1.1 -n envoy-gateway-system --create-namespace \
  --set deployment.replicas=3

helm upgrade eg oci://docker.io/envoyproxy/gateway-helm \
  --version v1.2.4 -n envoy-gateway-system \
  --set deployment.replicas=3

I will try to provide a demo yaml after my vacation, thank you @guydc

[ovaldi]

Hi @guydc I cannot reproduce this issue in the Test cluster, this issue can only reproduce in the Prod cluster. (Same K8s version & Same EG version)

Anyway, I will close this issue until I can reproduce it in the Test cluster.