RENOVATE_BOT
--- a/chart/README.md.gotmpl deleted 100644 → 0

+ 0

− 63
+++ b/chart/README.md.gotmpl deleted 100644 → 0

+ 0

− 63
-{{ template "chart.header" . }}
-
-{{ template "chart.versionBadge" . }}{{ template "chart.typeBadge" . }}{{ template "chart.appVersionBadge" . }}
-
-{{ template "chart.description" . }}
-
-{{ template "chart.sourcesSection" . }}
-
-{{ template "chart.requirementsSection" . }}
-
-{{ template "chart.valuesSection" . }}
-
-## Chart Repo
-
-Add the following repo to use the chart:
-
-```console
-helm repo add grafana https://grafana.github.io/helm-charts
-```
-
-## Installing the Chart
-
-To install the chart with the release name `my-release`:
-
-```console
-helm install my-release grafana/tempo
-```
-
-## Uninstalling the Chart
-
-To uninstall/delete the my-release deployment:
-
-```console
-helm delete my-release
-```
-
-The command removes all the Kubernetes components associated with the chart and deletes the release.
-
-## Upgrading
-
-A major chart version change indicates that there is an incompatible breaking change needing manual actions.
-
-### From Chart versions < 1.12.0
-
-Upgrading to chart 1.12.0 will set the memberlist cluster_label config option. During rollout your cluster will temporarilly be split into two memberlist clusters until all components are rolled out.
-This will interrupt reads and writes. This config option is set to prevent cross talk between Tempo and other memberlist clusters.
-
-### From Chart versions < 1.2.0
-
-Please be aware that we've updated the minor version to Tempo 2.1, which includes breaking changes.
-We recommend reviewing the [release notes](https://github.com/grafana/tempo/releases/tag/v2.1.0/) before upgrading.
-
-### From Chart versions < 1.0.0
-
-Please note that we've incremented the major version when upgrading to Tempo 2.0. There were a large number of
-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/) 
-and [1.5 -> 2.0 upgrade guide](https://grafana.com/docs/tempo/latest/setup/upgrade/) before upgrading.
-
-### From Chart versions < 0.7.0
-
-Upgrading from pre 0.7.0 will, by default, move your trace storage from `/tmp/tempo/traces` to `/var/tempo/traces`.
-This will cause Tempo to lose trace history. If you would like to retain history just copy the contents from the 
-old folder to the new.
 \ No newline at end of file