Docs mistake: enabling feature gates

[artem-nefedov]

Component(s)

No response

What happened?

Documentation currently contains an example on how to enable a feature gate via values in helm chart:

helm install opentelemetry-operator open-telemetry/opentelemetry-operator --set manager.featureGates=operator.autoinstrumentation.multi-instrumentation=enabled

If you try to use this example, controller won't be able to start, and will throw an error:

invalid argument "operator.autoinstrumentation.multi-instrumentation=enabled" for "--feature-gates" flag: no such feature gate "operator.autoinstrumentation.multi-instrumentation=enabled"

According to description of --feature-gates option, the correct way is without "=enabled" at the end (confirmed to work):

helm install opentelemetry-operator open-telemetry/opentelemetry-operator --set manager.featureGates=operator.autoinstrumentation.multi-instrumentation

 --feature-gates flag                               Comma-delimited list of feature gate identifiers. Prefix with '-' to disable the feature. '+' or no prefix will enable the feature. (default operator.autoinstrumentation.apache-httpd,operator.autoinstrumentation.dotnet,-operator.autoinstrumentation.go,operator.autoinstrumentation.java,-operator.autoinstrumentation.multi-instrumentation,-operator.autoinstrumentation.nginx,operator.autoinstrumentation.nodejs,operator.autoinstrumentation.python,operator.collector.rewritetargetallocator,-operator.observability.prometheus)

Kubernetes Version

Operator version

v0.89.0

Collector version

Environment information

No response

Log output

No response

Additional context

No response

[jaronoff97]

Yeah good catch – do you want to make the fix given it's minor? If not, I'll see if anyone else can make the change.

[artem-nefedov]

Sure, I'll post a PR