Replies: 1 comment 1 reply
-
Hi mitul01, maybe your arguments are ignored because they are not assigned to agent:
strategy: DaemonSet
options:
args:
- --reporter.type=grpc
- --reporter.grpc.host-port=wavefront-proxy.default:14250 Could you test this? |
Beta Was this translation helpful? Give feedback.
1 reply
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
I am trying to deploy a jaeger daemonset which collects traces and sends it to wavefront dashboard. As per the documentation I have installed jaeger operator and I'm using below yaml file to deploy a daemon set with updated args but the agent is still using the default args which is the jaeger collector.
The documentation provides an example of how to update the args in the manual sidecar method which I tried and it works successfully.
But I wanted to try the daemon set method since I have large number of pods and injecting a manual sidecar in each of the pods does not sound to be the most efficient method. But I'm not sure how to edit the arguments of the DaemonSet agent.
Below is the log which shows the daemonset connected to the default collector instead of the wavefront proxy that i provided.
Beta Was this translation helpful? Give feedback.
All reactions