README.md.gotmpl 1.6 KB

1234567891011121314151617181920212223242526272829303132333435363738394041424344454647484950515253
  1. {{ template "chart.header" . }}
  2. {{ template "chart.versionBadge" . }}{{ template "chart.typeBadge" . }}{{ template "chart.appVersionBadge" . }}
  3. {{ template "chart.description" . }}
  4. {{ template "chart.sourcesSection" . }}
  5. {{ template "chart.requirementsSection" . }}
  6. {{ template "chart.valuesSection" . }}
  7. ## Chart Repo
  8. Add the following repo to use the chart:
  9. ```console
  10. helm repo add grafana https://grafana.github.io/helm-charts
  11. ```
  12. ## Installing the Chart
  13. To install the chart with the release name `my-release`:
  14. ```console
  15. helm install my-release grafana/tempo
  16. ```
  17. ## Uninstalling the Chart
  18. To uninstall/delete the my-release deployment:
  19. ```console
  20. helm delete my-release
  21. ```
  22. The command removes all the Kubernetes components associated with the chart and deletes the release.
  23. ## Upgrading
  24. A major chart version change indicates that there is an incompatible breaking change needing manual actions.
  25. ### From Chart versions < 1.0.0
  26. Please note that we've incremented the major version when upgrading to Tempo 2.0. There were a large number of
  27. changes in this release (breaking and otherwise). It is encouraged to review the [release notes](https://grafana.com/docs/tempo/latest/release-notes/v2-0/)
  28. and [1.5 -> 2.0 upgrade guide](https://grafana.com/docs/tempo/latest/setup/upgrade/) before upgrading.
  29. ### From Chart versions < 0.7.0
  30. Upgrading from pre 0.7.0 will, by default, move your trace storage from `/tmp/tempo/traces` to `/var/tempo/traces`.
  31. This will cause Tempo to lose trace history. If you would like to retain history just copy the contents from the
  32. old folder to the new.