ravi-dd

> I have developed a modified Vimium (I call it [Vimium C](https://github.com/gdh1995/vimium-c)), and it can config many details. You may have a try. > > On Vimium C, you may...

> have u got large input artifact? I used to have OOM on it but setting my init container to 160MB fixed it How did you set the initcontainer memory?

@adisuissa, related to https://github.com/envoyproxy/envoy/pull/41117

Does the same concern apply to enabling resource tracking for the SoTW API, `cds_api_impl.cc` similar to https://github.com/envoyproxy/envoy/pull/41117, either config flagged or by default? This solves the mentioned SoTW ODCDS interaction...

My high level goal is to prevent CDS SotW from removing OD CDS clusters. https://github.com/envoyproxy/envoy/pull/41117 does exactly this _but only for ODCDS over xDS-TP_ (`support_multi_ads_sources` enables tracking for `CdsApi` but...

Hey @adisuissa, following up on this. Thanks

I see what you mean. Is it not possible to leverage `sotw_resource_names_` [here](https://github.com/envoyproxy/envoy/blob/main/source/common/upstream/cds_api_impl.h#L79) though or is that only meant to be temporary and not the proper way to handle it?