Envoy Gateway: How to I set Upstream timeout?

[SAAMalusare]

Hello,

We are now migrating from Ingress-Nginx controller to EnvoyGateway + GatewayAPI.
I would like to replicate the below timeouts in my new setup:

nginx.ingress.kubernetes.io/proxy-connect-timeout: "3"
nginx.ingress.kubernetes.io/proxy-next-upstream: error timeout http_502 http_503 http_504
nginx.ingress.kubernetes.io/proxy-next-upstream-timeout: "10"
nginx.ingress.kubernetes.io/proxy-next-upstream-tries: "3"

My HttpRoute:

`
apiVersion: gateway.networking.k8s.io/v1
kind: HTTPRoute
metadata:
name: httproute-myapp
namespace: dt
spec:
parentRefs:

• name: egw
  namespace: egw-system
  hostnames:
• services-egw-pods.mycomp.com
  rules:
• matches:
  • path:
    type: PathPrefix
    value: /myapp
    backendRefs:
  • name: svc-myapp-api
    port: 80
    retry:
    codes: [ 500, 502, 503, 504 ]
    attempts: 3
    backoff: 500ms
    `

test-httprout.yaml

Is this correct? how do I test this?

Warm regards,
Suhas

[arkodg]

cc @kkk777-7

[SAAMalusare]

Hi @arkodg, I was able to apply and test. This was implemented via BackendTrafficPolicy

And tested via command: egctl x stats envoy-proxy

`egctl x stats envoy-proxy -n egw-system envoy-egw-system-egw-e19ab3c3-74b976b5f9-vzdk7 | egrep upstream_rq_retry

TYPE envoy_cluster_upstream_rq_retry_limit_exceeded counter

envoy_cluster_upstream_rq_retry_limit_exceeded{envoy_cluster_name="EmptyCluster"} 0
envoy_cluster_upstream_rq_retry_limit_exceeded{envoy_cluster_name="egw-system/egw"} 0
envoy_cluster_upstream_rq_retry_limit_exceeded{envoy_cluster_name="httproute/dt/httproute-mysvc/rule/0"} 3
envoy_cluster_upstream_rq_retry_limit_exceeded{envoy_cluster_name="prometheus_stats"} 0
envoy_cluster_upstream_rq_retry_limit_exceeded{envoy_cluster_name="xds_cluster"} 0

`