Add steps to use Tempo as tracing storage via Tempo operator #677
Conversation
|
netlify link for reviewers to look at: https://deploy-preview-677--kiali.netlify.app/docs/configuration/p8s-jaeger-grafana/jaeger/#use-jaeger-frontend-with-grafana-tempo-tracing-backend |
| provides a native Kubernetes solution to deploy Tempo easily in your system. | ||
|
|
||
| After installing the Tempo Operator in your cluster, you can create a new | ||
| Tempo instance with the following CRD: |
There was a problem hiding this comment.
This is not a CRD (a CustomResourceDefinition).. this is an instance of the tempo CRD - aka a "Custom Resource" or CR:
| Tempo instance with the following CRD: | |
| Tempo instance with the following CR: |
There was a problem hiding this comment.
Ooops. I typed too fast. Thanks!
|
Thanks @iblancasa ! Last week we had a user get things working as described here, does that look correct to you, and does the PR cover his configuration? |
I covered here the creation of a Tempo instance using the Kubernetes Operator. That description uses Helm. I think we should cover both. Also the method described in the official Tempo documentation. But as part of different PRs to make it easier to give feedback/review. Sorry anyway for the delay. Lot of stuff in progress. |
jshaughn
changed the title
Ah, I see, thanks. This looks good to ne but I added @aljesusg as a reviewer. GIven your feedback I added two more subtasks to the Epic kiali/kiali#5850. One for Helm and one for Tempo docs. Will you be able to help with those as well? |
Yes. I'll try my best :D |
Add a new section to explain how to use Tempo (with the Tempo Operator) as tracing storage.
Later, we can add more sections about how to do the same using Heml or other deployment modes that can be interesting for the users.