Grafana Tempo packaged by Bitnami¶

Grafana Tempo is a distributed tracing system that has out-of-the-box integration with Grafana. It is highly scalable and works with many popular tracing protocols.

Overview of Grafana Tempo

Trademarks: This software listing is packaged by Bitnami. The respective trademarks mentioned in the offering are owned by the respective companies, and use of them does not imply any affiliation or endorsement.

TL;DR¶

使用加速地址添加仓库:

helm repo add bitnami "https://helm-charts.itboon.top/bitnami" --force-update
helm update bitnami

helm install my-release bitnami/grafana-tempo

Introduction¶

Bitnami charts for Helm are carefully engineered, actively maintained and are the quickest and easiest way to deploy containers on a Kubernetes cluster that are ready to handle production workloads.

This chart bootstraps a Grafana Tempo Deployment in a Kubernetes cluster using the Helm package manager.

Bitnami charts can be used with Kubeapps for deployment and management of Helm Charts in clusters.

Learn more about the default configuration of the chart.

Looking to use Grafana Tempo in production? Try VMware Application Catalog, the enterprise edition of Bitnami Application Catalog.

Prerequisites¶

• Kubernetes 1.19+
• Helm 3.2.0+
• PV provisioner support in the underlying infrastructure

Installing the Chart¶

To install the chart with the release name my-release:

helm install my-release bitnami/grafana-tempo

The command deploys grafana-tempo on the Kubernetes cluster in the default configuration. The Parameters section lists the parameters that can be configured during installation.

Tip: List all releases using helm list

Uninstalling the Chart¶

To uninstall/delete the my-release deployment:

helm delete my-release

The command removes all the Kubernetes components associated with the chart and deletes the release.

Parameters¶

Global parameters¶

Common parameters¶

Common Grafana Tempo Parameters¶

Compactor Deployment Parameters¶

Compactor Traffic Exposure Parameters¶

Distributor Deployment Parameters¶

Distributor Traffic Exposure Parameters¶

Metrics Generator Deployment Parameters¶

Metrics Generator Traffic Exposure Parameters¶

Ingester Deployment Parameters¶

Ingester Persistence Parameters¶

Ingester Traffic Exposure Parameters¶

Querier Deployment Parameters¶

Querier Traffic Exposure Parameters¶

Query Frontend Deployment Parameters¶

Query Frontend Traffic Exposure Parameters¶

Vulture Deployment Parameters¶

Vulture Traffic Exposure Parameters¶

Init Container Parameters¶

Other Parameters¶

Metrics Parameters¶

External Memcached Parameters¶

Memcached Sub-chart Parameters¶

Specify each parameter using the --set key=value[,key=value] argument to helm install. For example,

helm install my-release \
  --set tempo.traces.jaeger.grpc=true \
  bitnami/grafana-tempo

The above command enables the Jaeger GRPC traces.

Alternatively, a YAML file that specifies the values for the above parameters can be provided while installing the chart. For example,

helm install my-release -f values.yaml bitnami/grafana-tempo

Tip: You can use the default values.yaml

Configuration and installation details¶

Rolling VS Immutable tags¶

It is strongly recommended to use immutable tags in a production environment. This ensures your deployment does not change automatically if the same tag is updated with a different image.

Bitnami will release a new chart updating its containers if a new version of the main container, significant changes, or critical vulnerabilities exist.

Tempo configuration¶

The tempo configuration file tempo.yaml is shared across the different components: distributor, compactor, ingester, querier and queryFrontend. This is set in the tempo.configuration value. Check the official Tempo Grafana documentation for the list of possible configurations.

Persistence¶

The Bitnami grafana-tempo image stores the grafana-tempo ingester data at the /bitnami path of the container. Persistent Volume Claims are used to keep the data across deployments.

Additional environment variables¶

In case you want to add extra environment variables (useful for advanced operations like custom init scripts), you can use the extraEnvVars property inside each of the subsections: distributor, compactor, ingester, querier, queryFrontend and vulture.

compactor:
  extraEnvVars:
    - name: LOG_LEVEL
      value: error

distributor:
  extraEnvVars:
    - name: LOG_LEVEL
      value: error

ingester:
  extraEnvVars:
    - name: LOG_LEVEL
      value: error

querier:
  extraEnvVars:
    - name: LOG_LEVEL
      value: error

queryFrontend:
  extraEnvVars:
    - name: LOG_LEVEL
      value: error

vulture:
  extraEnvVars:
    - name: LOG_LEVEL
      value: error

Alternatively, you can use a ConfigMap or a Secret with the environment variables. To do so, use the extraEnvVarsCM or the extraEnvVarsSecret values.

Sidecars¶

If additional containers are needed in the same pod as grafana-tempo (such as additional metrics or logging exporters), they can be defined using the sidecars parameter inside each of the subsections: distributor, compactor, ingester, querier, queryFrontend and vulture . If these sidecars export extra ports, extra port definitions can be added using the service.extraPorts parameter. Learn more about configuring and using sidecar containers.

Pod affinity¶

This chart allows you to set your custom affinity using the affinity parameter. Find more information about Pod affinity in the kubernetes documentation.

As an alternative, use one of the preset configurations for pod affinity, pod anti-affinity, and node affinity available at the bitnami/common chart. To do so, set the podAffinityPreset, podAntiAffinityPreset, or nodeAffinityPreset parameters inside each of the subsections: distributor, compactor, ingester, querier, queryFrontend and vulture.

External cache support¶

You may want to have Grafana Tempo connect to an external Memcached rather than installing one inside your cluster. Typical reasons for this are to use a managed cache service, or to share a common cache server for all your applications. To achieve this, the chart allows you to specify credentials for an external database with the externalMemcached parameter. You should also disable the Memcached installation with the memcached.enabled option. Here is an example:

memcached.enabled=false
externalMemcached.host=myexternalhost
externalMemcached.port=11211

Troubleshooting¶

Find more information about how to deal with common errors related to Bitnami's Helm charts in this troubleshooting guide.

Upgrading¶

To 2.0.0¶

This major release removes search_enabled and metrics_generator_enabled configuration parameters, assuming they are always enabled.

To 1.0.0¶

This major release renames several values in this chart and adds missing features, in order to be inline with the rest of assets in the Bitnami charts repository.

• tempo.containerPort, tempo.grpcContainerPort and tempo.gossipRing.containerPort have been regrouped under the tempo.containerPorts map.
• queryFrontend.query.jaegerMetricsContainerPort and queryFrontend.query.jaegerUIContainerPort have been regrouped under the queryFrontend.query.containerPorts map.
• vulture.containerPort has been regrouped under the vulture.containerPorts map.
• XXX.service.port and XXX.service.grpcPort have been regrouped under the XXX.service.ports map.

Additionally updates the Memcached subchart to its newest major 6.x.x, which contains similar changes.

License¶

Copyright © 2023 VMware, Inc.

Licensed under the Apache License, Version 2.0 (the "License"); you may not use this file except in compliance with the License. You may obtain a copy of the License at

http://www.apache.org/licenses/LICENSE-2.0

Unless required by applicable law or agreed to in writing, software distributed under the License is distributed on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the License for the specific language governing permissions and limitations under the License.