You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
From DataDog/datadog-operator@4bc766f (I believe this is v1.8.0) to the most recent release of this writing (v1.11.1) there is no mechanism to add the command line arg otelEnabled to the deployment created in this chart to enable OTeL support.
The arguments passed are tightly controlled by what is present in Values.
Proposal
Expose through Values an additionalCommandArgs that allow users to specify additional flags/args at their own risk. For users of the operator v1.8-v1.11.1 this will allow them to enable OTeL (and any other features currently not configurable through the operator config or the helm chart).
Considerations
Currently in main (but unreleased) the operator adds OTeL as a "default" feature DataDog/datadog-operator#1559, and it removes this arg as a "non-breaking" change. Given that it wasn't exposed, that's probably correct, but the additionalCommandArgs (or whatever it might be called) should likely recommend caution (and perhaps even pinning operator versions) if it's leveraged.
The text was updated successfully, but these errors were encountered:
wspurgin
changed the title
datadog-opeartor No mechanism exists to enable OTeL for operator versions ~v1.8.0<=x<=v1.11.1
datadog-opeartor No mechanism exists to enable OTeL Collector for operator versions ~v1.8.0<=x<=v1.11.1
Jan 3, 2025
Problem
From DataDog/datadog-operator@4bc766f (I believe this is v1.8.0) to the most recent release of this writing (v1.11.1) there is no mechanism to add the command line arg
otelEnabled
to the deployment created in this chart to enable OTeL support.e.g., for the latest release of this chart (2.5.0) https://github.com/DataDog/helm-charts/blob/datadog-operator-2.5.0/charts/datadog-operator/templates/deployment.yaml#L104-L137
The arguments passed are tightly controlled by what is present in
Values
.Proposal
Expose through
Values
anadditionalCommandArgs
that allow users to specify additional flags/args at their own risk. For users of the operator v1.8-v1.11.1 this will allow them to enable OTeL (and any other features currently not configurable through the operator config or the helm chart).Considerations
Currently in
main
(but unreleased) the operator adds OTeL as a "default" feature DataDog/datadog-operator#1559, and it removes this arg as a "non-breaking" change. Given that it wasn't exposed, that's probably correct, but theadditionalCommandArgs
(or whatever it might be called) should likely recommend caution (and perhaps even pinning operator versions) if it's leveraged.The text was updated successfully, but these errors were encountered: