Global configuration supports upstream idle timeout

[johnlanni]

Why do you need it?

Envoy's default upstream idle timeout is 1 hour. When the backend closes the connection in advance, it is easy to send a request when the connection is closed, causing problems such as 503.

How could it be?

global config：

upstream:
  idleTimeout: 10s

envoyfilter ：

apiVersion: networking.istio.io/v1alpha3
kind: EnvoyFilter
metadata:
  name: upstream-idle-timeout
  namespace: higress-system
spec:
  configPatches:
  - applyTo: CLUSTER
    match:
      context: GATEWAY
    patch:
      operation: MERGE
      value:
        common_http_protocol_options:
          idle_timeout: 10s

Other related information

https://www.envoyproxy.io/docs/envoy/v1.20.3/api-v3/config/cluster/v3/cluster.proto

https://www.envoyproxy.io/docs/envoy/v1.20.3/api-v3/config/core/v3/protocol.proto#envoy-v3-api-msg-config-core-v3-httpprotocoloptions

[sjcsjc123]

I can work it.