Closed johnlanni closed 2 months ago
The suspicion that HTTPS is causing the leak arises because we have deployed multiple envoy instances, and only those handling HTTPS traffic exhibit memory leaks. We attempted to revert the BoringSSL version back to the one used in 1.23, but the issue persists.
Identified the issue as being related to Istio: https://github.com/istio/istio/issues/52850
Description:
After we upgraded Envoy from version 1.23 to 1.27, we observed a memory leak in the gateway handling HTTPS traffic. However, we were unable to reproduce the issue consistently in an offline environment. Consequently, we proceeded to upgrade Envoy further to version 1.31.0, only to find that the memory leakage problem persisted.
Heap profiler (1.27.2): leak-1.27.2.pdf
Heap profiler (1.31.0): leak-1.31.0.pdf
Envoy Config
LDS config snippet:
RDS config snippet:
CDS config snippet:
SDS config snippet:
Connection tracing log
proxy.log