Consul - override default timeout of envoys

[MiladiHedi]

hello,
I’m working on Consul 1.20 on a Kubernetes cluster.
I have a problem that I can’t solve: all requests are blocked at 5 minutes by a timeout, and I receive a 504 error.

My goal is to have requests every hour (I know, it might seem strange, but that’s what I need).

I have a global proxy-defaults.yaml

ApiVersion: consul.hashicorp.com/v1alpha1
kind: ProxyDefaults
metadata:
  name: global
  namespace: consul
spec:
  config:
    local_request_timeout_ms: 3600000
    local_idle_timeout_ms: 3600000

and for each service:

• a service-defaults.yaml and

apiVersion: consul.hashicorp.com/v1alpha1
kind: ServiceDefaults
metadata:
  name: my-service
  namespace: consul
spec:
  protocol: http
  localRequestTimeoutMs : 3600000

• a service-resolver.yaml

apiVersion: consul.hashicorp.com/v1alpha1
kind: ServiceResolver
metadata:
  name: my-service
  namespace: consul
spec:
  requestTimeout: 3600s

Regarding Envoy documentation, I identify the only one default timeout that’s set to 5 minutes is : stream_idle_timeout ( How do I configure timeouts? — envoy 1.37.0-dev-346db8 documentation )
I was looking for how to override this timeout, and in my research I came across this post that talks about the same problem: Override stream_idle_timeout 5 min default on envoy , someone pushed this PR : Adds idle_timeout envoy proxy local app config knob by johnalotoski · Pull Request #14418 · hashicorp/consul · GitHub on the Consul repository and it was released in v1.14 (as a reminder, I’m on Consul 1.20)

In the code, we can see :

// LocalIdleTimeoutMs is the number of milliseconds a request's stream to the
// local app instance may be idle. If not set, no value is set, Envoy defaults
// are respected, and an Envoy stream_idle_timeout (5m) will apply. If set,
// this LocalIdleTimeoutMs value will override the Envoy stream_idle_timeout.

Add support for configuring Envoys route idle_timeout

As written above, I put this value in the default proxy.

As its explained in PR Conversation ( Add support for configuring Envoys route idle_timeout by oulman · Pull Request #14340 · hashicorp/consul · GitHub ),
I tried as well, to add a service router on my-service :

apiVersion: consul.hashicorp.com/v1alpha1
kind: ServiceRouter
metadata:
 name: my-service
spec:
 routes:
   - destination:
       idleTimeout: 3600s
       requestTimeout: 3600s
       service: ''

but after dumping config of the envoy of my-service i didn’t find any occurence of idle timeout.

I’m still blocked and my objective is to have requests between services that can reach one hour.

What’s wrong, what should I do?

Please could you help me to solve this issue.
Thank you in advance.

Regards