Mikołaj Świątek

> @swiatekm anything missing? We're still waiting for the change to prometheus receiver so that e2e tests here can pass, right?

> > > @swiatekm anything missing? > > > > > > We're still waiting for the change to prometheus receiver so that e2e tests here can pass, right? >...

> > 👍 Thank you for all the work you've put into this change (and the related ones elsewhere)! I've left some questions about config handling in the Target Allocator,...

We should just pin the envtest version to the latest one which supports Go 1.21. This is another example of how #2757 can affect us.

Can you try enabling the `operator.targetallocator.mtls` feature gate for the operator? Authenticated endpoints are not supported without that flag. See https://github.com/open-telemetry/opentelemetry-operator/tree/main/cmd/otel-allocator#service--pod-monitor-endpoint-credentials for more information.

Unfortunately, this only works with cert-manager enabled at the moment. Otherwise, the target allocator does not support authenticated Prometheus endpoints.

Could you go into more detail about what exactly you'd like to the operator to support? Are we talking about a separate CRD for the EBPF collector?

From what I understand, the EBPF stack is a set of applications which can ultimately emit metrics via OTLP. If we wanted to directly support this, I think we'd introduce...

Can you post your `values.yaml`? It looks like you're trying to use the target allocator image where the collector image is expected.

The main barrier towards supporting each Go version until EOL are dependencies. In particular, as seen in #2741, prometheus-operator packages can be quite aggressive when it comes to bumping their...