The OTEL operator 0.142.0 removed depenrency on the kube-rback-proxy. The authentication and authorization is now handled by the native controller runtime implementation.

• kube-rbac-proxy references https://github.com/search?q=repo%3Aopen-telemetry%2Fopentelemetry-helm-charts%20kube-rbac-proxy&type=code
• operator PR Remove kube-rbac-proxy and use builtin controller-runtime approach opentelemetry-operator#4576

Users should not directly depend on the kube-rbac-proxy. The proxy just provides auth for the /metrics operator endpoint.