My company and I are users of Istio，now the memory of the istio-proxy is too big, and we can find it because the envoy caches a lot of the configuration of the application. Envoys start a lot of listening because of the large clusters and the number of PODs in namespaces. And in our micro-service model, it is almost impossible to understand the invocation relationships between services. So we can’t issue the configuration on demand. The Envoy only caches the full configuration.
After investigating the envoy delta interface can lazy load configuration. Someone has already mentioned this issue. Support delta_grpc ADS API · Issue #19681 · istio/istio · GitHub
I would like to know the progress and attitude of the Istio community at present. I want to be a part of it if I can.