Verify Envoy recommendations as an edge proxy

[pubudu538]

Describe your problem(s)

Verify Envoy recommendations for CC - https://www.envoyproxy.io/docs/envoy/latest/configuration/best_practices/edge#best-practices-edge

Describe your solution

How will you implement it

---

Optional Fields

Related Issues:

Suggested Labels:

Suggested Assignees:

[NomadXD]

1. use_remote_address - Implemented in #2959

2. overload_manager - Ignored

Prevent crashing due to OOM errors by rejecting new connections or closing down connections. No extra benefit compared to K8s deployment with liveness probe. Also not possible to configure with xDS since this falls under bootstrap config. Therefore ignored.

3. Listener buffer limits / Cluster buffer limits - Ignored

Both listener buffer limit and cluster limit are soft limits in envoy. So the existing connections are not closed depending on the buffer value. Buffer value is only used for watermark and drain implementation to copy request/response bytes. For edge proxy config, the recommendation is to set per_connection_buffer_limit_bytes to 32 KiB. But for large payloads, it takes more time to copy and it raises concerns regarding timeouts.

4. Connection and Stream timeouts - Already configured under route config

5. HTTP/2 related config - Added in #2953

6. Global downstream connection limits - Already configured to 2147483647

7. headers_with_underscores_action setting - Ignored

8. path_with_escaped_slashes_action setting - Ignored

cc @pubudu538 @VirajSalaka

[pubudu538]

As we have addressed the concerns above I am closing the issue.