Generally speaking, I'm not the biggest fan of the operator pattern that has emerged in the Kubernetes space. Don't get me wrong, the approach taken has some great use cases, but I often find many of them to be simple shims that are no better than a Helm chart (see the operator maturity model).
The OpenTelemetry operator has a few really nice features that make it really appealing such as:
auto-instrumentation
sidecar injection
Adding the operator and custom resources will add a fair bit of complexity (I know its a fairly big problem I have with the kube-prometheus-stack solution).
We'll want to prototype its integration into the system... maybe do it as a new chart (cognative-operator?) to keep a "minimalist" approach and a separate one for a fuller solution.
Repository https://github.com/open-telemetry/opentelemetry-operator
Generally speaking, I'm not the biggest fan of the operator pattern that has emerged in the Kubernetes space. Don't get me wrong, the approach taken has some great use cases, but I often find many of them to be simple shims that are no better than a Helm chart (see the operator maturity model).
The OpenTelemetry operator has a few really nice features that make it really appealing such as:
Adding the operator and custom resources will add a fair bit of complexity (I know its a fairly big problem I have with the kube-prometheus-stack solution).
We'll want to prototype its integration into the system... maybe do it as a new chart (
cognative-operator?) to keep a "minimalist" approach and a separate one for a fuller solution.