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
We want traces to be exporter to OTEL collector running on the same host/node. For that purpose we use downward API to get status.hostIP and reference it in OTEL_EXPORTER_OTLP_ENDPOINT end, but OTEL operator does not resolve it and exporter gets invalid IP.
After looking at the source code implementation, I think there might be some misunderstanding here.
By design both nodejs.env and Instrumentation spec.env end up injecting pod container[0].env. No string substitution occurs during the injection process. Therefore, the value of OTEL_EXPORTER_OTLP_ENDPOINT will always be "http://$(OTEL_EXPORTER_HOST_IP):4317".
Component(s)
auto-instrumentation
What happened?
Description
We want traces to be exporter to OTEL collector running on the same host/node. For that purpose we use downward API to get
status.hostIP
and reference it inOTEL_EXPORTER_OTLP_ENDPOINT
end, but OTEL operator does not resolve it and exporter gets invalid IP.Steps to Reproduce
Expected Result
Env
OTEL_EXPORTER_OTLP_ENDPOINT
should contain correct address with host ip.Actual Result
Env
OTEL_EXPORTER_OTLP_ENDPOINT
contains string ashttp://$(OTEL_EXPORTER_HOST_IP):4317
instead which is not resolved.Kubernetes Version
1.28
Operator version
version: 0.47.0 appVersion: 0.93.0
Collector version
Custom
Environment information
No response
Log output
No response
Additional context
No response
The text was updated successfully, but these errors were encountered: