Closed bc185174 closed 2 months ago
Hi @bc185174 – how exactly are you deploying and meshing Prometheus? There are a few too many ways of doing that to just run with "deploy and mesh Prometheus"...
Hi @bc185174 – how exactly are you deploying and meshing Prometheus? There are a few too many ways of doing that to just run with "deploy and mesh Prometheus"...
Apologies - we are deploying it via the prometheus operator https://github.com/prometheus-operator/prometheus-operator. Then deploy linkerd 2.14.10
and auto mesh the prometheus pods.
OK, I think the immediate questions here are:
Thanks!
Closing this one; please reopen if you're still having this issue and can provide more details.
What is the issue?
We have prometheus deployed and the destination controller is spamming these logs:
It only applies to the prometheus namespace and there are no other namespaces reporting this log.
How can it be reproduced?
Deploy prometheus operator and mesh it with Linkerd.
Logs, error output, etc
output of
linkerd check -o short
N/A
Environment
Possible solution
No response
Additional context
No response
Would you like to work on fixing this bug?
maybe