Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Installation on existing cluster fails with "could not initialize jaeger tracer: lookup grafana-agent-traces.default.svc.cluster.local on some-ip:53: no such host" #40

Closed
mauricewittek opened this issue Aug 5, 2022 · 1 comment

Comments

@mauricewittek
Copy link

I tried deploying the app on an existing cluster following the guide. After running the install script, all 3 pods keep crashing. The logs show the same error message for all 3 pods: level=error msg="error initializing tracing" err="could not initialize jaeger tracer: lookup grafana-agent-traces.default.svc.cluster.local on 10.245.0.10:53: no such host"

I tried deploying the app to two different clusters, on on Civo (v1.22.11+k3s1) and the other one on DigitalOcean (Kubernetes 1.23.9-do.0).

@mauricewittek
Copy link
Author

My mistake, I had two problems in my cluster:

I didn't check if the grafana-agent-traces Pod was running before deploying the app. The tracer needed 12 minutes to go from containerCreating to running state in my cluster which was unexpected.

After the tracer was running I had to change the value of JAEGER_AGENT_HOST in the 3 deployments as my tracer agent wasn't installed in the default namespace.

Now it works.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant