Lorenzo Biava

@vvanholl would a PR from @mindw 's fork help implementing the support for v8 in your repo? or do you have other plans?

Removing a few jobs that weren't scraping any targets (~20) did actually reduce the CPU load significantly (~3 vCPU) 

Here's the log from the past few days, including startup (I'm seeing a lot of K8s API errors, which I believe are related to transient instability of that managed cluster)....

@roidelapluie thanks for the suggestion; can you point me to an example of such config? I then need to check if that's possible via PromOp ServiceMonitors or something similar... I...

So basically I need to get rid of the namespace in the `kubernetes_sd_configs` and add a `relabel_configs` to filter the namespace. I believe that's not (currently) possible with ServiceMonitors, not...

So we managed to merge together a lot of ServiceMonitors. Even though they were all scraping the same namespace, we got an impressive reduction in CPU usage (less than half;...

> Actually, this hard work is doing per service monitor. So if you have 30 of them, you have x30 useless work. It's definitely amplified by the number of Service...

For us it was definitely CPU (as per the title of the issue). Not sure about RAM, haven't seen any correlation with a change in memory usage yet. PS: All...

@keithmattix Similar situation. All bootstrap secrets are missing OwnerRef and are left behind. I can see these logs from https://github.com/openservicemesh/osm/blob/v1.2.1/pkg/k8s/announcement_handlers.go#L57 : ```Failed to get secret fabric-benchmark/envoy-bootstrap-config- mounted to Pod fabric-benchmark/apps-sync-job-ccss-poller-benchmark-27800000-9hz2s```...

I think in general it's great to build on existing components, without reinventing the wheel. At the same time, a sidecar just for implementing TLS termination (which is typically done...