-
Bug
-
Resolution: Done
-
Undefined
-
None
-
Quality / Stability / Reliability
-
1
-
False
-
-
False
-
-
-
Tracing Sprint # 277 - 3.7
With an invalid (or missed) endpoint configuration in the receiver configuration of
receivers:
otlp:
protocols:
grpc:
endpoint: '0.0.0.0'
the Operator does not reconcile the CR to the default port and instead appends the listen address as Port which creates an invalid Socket tuple
receivers:
otlp:
protocols:
grpc:
endpoint: '0.0.0.0:0.0.0.0'
this ends as Error on pod restart seen like
Error: cannot start pipelines: failed to start "otlp" receiver: listen tcp: lookup tcp/0.0.0.0: unknown port 2025/09/22 16:16:19 collector server run finished with error: cannot start pipelines: failed to start "otlp" receiver: listen tcp: lookup tcp/0.0.0.0: unknown port
The Network policy related to the Collector get's reconciled to the default port as expected.