How to configure gRPC protocol listener on Service Mesh envoyProxy sidecar

Issue

gRPC applications using bi-directional streams between client and server causes huge memory usage from istio-proxy envoy sidecar.
Even when using circuit breaker to implement http2MaxRequests the sidecar keeps consuming memory until its limits.
In order to make it work the sidecar memory limits have to be increase to values that are not acceptable and the default value of 2Gi causes the container to constantly crash.