After the OpenTelemetry SDK has changed it's handling of metrics coming over a prometheus bridge (open-telemetry/opentelemetry-go#7688), none of the metrics coming from controller-runtime or kube-apiserver Registries if otel is set to use it's Prometheus exporter.
I have proposed a solution for this towards the otel-autoexports package: open-telemetry/opentelemetry-go-contrib#9124.
If that doesn't go through, and Porch should still have a single metric export endpoint, then it would require setting up a separate prometheus metrics endpoint that serves both otel provided and kube-apiserver provided metrics.
After the OpenTelemetry SDK has changed it's handling of metrics coming over a prometheus bridge (open-telemetry/opentelemetry-go#7688), none of the metrics coming from
controller-runtimeorkube-apiserverRegistries if otel is set to use it's Prometheus exporter.I have proposed a solution for this towards the otel-autoexports package: open-telemetry/opentelemetry-go-contrib#9124.
If that doesn't go through, and Porch should still have a single metric export endpoint, then it would require setting up a separate prometheus metrics endpoint that serves both otel provided and kube-apiserver provided metrics.