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
With the latest release (v0.15.0), I get the following error in all OTel collector pods when deploying with the OpenTelemetry Operator:
$ kubectl logs dynatrace-otel-collector-...
Error: invalid argument "-component.UseLocalHostAsDefaultHost" for "--feature-gates" flag: feature gate "component.UseLocalHostAsDefaultHost" is stable, can not be disabled
2024/09/27 12:32:55 collector server run finished with error: invalid argument "-component.UseLocalHostAsDefaultHost" for "--feature-gates" flag: feature gate "component.UseLocalHostAsDefaultHost" is stable, can not be disabled
My deployment is mostly aligned with the Dynatrace OTel collector deployment docs, with the main difference that I use mode: "daemonset" (see below). With v0.14.0 everything works fine.
I deploy the Dynatrace OTel Collector with the OpenTelemetry Operator according to the steps described in Dynatrace OTel collector deployment docs with Deploy as an agent (DaemonSet). My OpenTelemetryCollector manifest looks like this:
Describe the bug
With the latest release (v0.15.0), I get the following error in all OTel collector pods when deploying with the OpenTelemetry Operator:
My deployment is mostly aligned with the Dynatrace OTel collector deployment docs, with the main difference that I use
mode: "daemonset"
(see below). With v0.14.0 everything works fine.I assume this is related to open-telemetry/opentelemetry-operator#3306.
To Reproduce
I deploy the Dynatrace OTel Collector with the OpenTelemetry Operator according to the steps described in Dynatrace OTel collector deployment docs with Deploy as an agent (DaemonSet). My
OpenTelemetryCollector
manifest looks like this:Expected behavior
I expected that on each Kubernetes node a pod
dynatrace-otel-collector-...
is successfully started.Additional context
I am using Kubernetes version 1.29 in AWS EKS.
The text was updated successfully, but these errors were encountered: