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
Describe the bug
I tried to deploy the relevant components of otel in my k8s cluster using examples/k8s/otel-config.yaml, but I realized that the default IP for service startup is bound to its own POD. I think the configurations in these two ConfigMaps: otel-collector-conf and otel-agent-conf are as follows:
Describe the bug
I tried to deploy the relevant components of otel in my k8s cluster using
examples/k8s/otel-config.yaml
, but I realized that the default IP for service startup is bound to its own POD. I think the configurations in these two ConfigMaps:otel-collector-conf
andotel-agent-conf
are as follows:Is it more appropriate to change it to
0.0.0.0
?Steps to reproduce
Up
What version did you use?
v0.100.0
What config did you use?
examples/k8s/otel-config.yaml
Environment
K8s v1.19.9
Additional context
None
The text was updated successfully, but these errors were encountered: