Tyler Helmuth

@ferrucc-io Can you be more specific with what docs were confusing?

@AlecAttwood the OpenTelemetry Operator does not support being run as a Daemonset. Can you describe more how pods are starting before the Operator? Is the Operator deployment getting evicted and...

I think Topology is definitely what you want. If the chart allowed installing the operator as a daemonset we'd be deploying the operator in a pattern unsupported by the OpenTelemetry...

Other @open-telemetry/operator-approvers please chime in, but I believe having multiple operators managing the same webhooks/custom resources would create a problem. In general I think K8s Operators are not run as...

@dmitryax @mx-psi can you share more about the goal of this extension?

You're not wrong, but also I don't have a great solution in mind for this other than don't use decimals. Maybe https://github.com/open-telemetry/opentelemetry-collector-contrib/issues/30289 can help

@Only-a-User I was not able to reproduce this issue. With the latest version of the chart and this values.yaml, everything is rendered as expected: ```yaml mode: daemonset config: service: pipelines:...

What version of the chart are you using?

Ok I definitely suspect this is an issue with your helm version then. Are you able to reproduce the issue locally with a known helm version?

Can you try completely removing the crds