[{"_1":2,"_135":-5,"_136":-5},"loaderData",{"_3":4,"_13":14,"_21":22,"_129":130},"root",{"_5":-5,"_6":-7,"_7":8,"_9":-7,"_10":11,"_12":-7},"currentUser","primaryEmail","siteVerification","6LeIxAcTAAAAAJcZVRqyHh71UMIEGNQ_MXjiZKhI","toast","enableDev",false,"incidentStatus","routes/_layout",{"_15":-5,"_16":17,"_18":17,"_19":11,"_20":11},"username","isAskGordonEnabled",true,"isUsingNewTemplate","showMinimalLanding","showHoneypotTrap","routes/_layout.layers.$namespace.$reponame.$tag.(images).($imageUrlDigest)",{"_23":24,"_25":26,"_55":56,"_57":-7,"_58":-7,"_59":-7,"_60":-7,"_61":-5,"_62":-5,"_63":11,"_64":11,"_48":65,"_119":17,"_87":88,"_120":86,"_121":47,"_31":32,"_122":11,"_123":17,"_124":125,"_126":-5,"_127":11,"_128":11},"scanningType","none","tagData",{"_27":28,"_29":30,"_31":32,"_33":34,"_35":36,"_37":38,"_39":40,"_41":30,"_42":43,"_44":45,"_46":47,"_48":49,"_50":-5,"_51":40,"_52":53,"_54":17},"content_type","image","creator",35095401,"digest","sha256:d0995b8823690e16253680c427b15f3e631c8350fdd256ff507b3656a97f4261","full_size",7947,"id",914696056,"images",[],"last_updated","2025-06-10T20:28:12.926518Z","last_updater","last_updater_username","bitnamibot508","media_type","application/vnd.oci.image.index.v1+json","name","sha256-77ad745045e2d15212fb727bb3d2da4022bc9902aacd0b170ba1b513b07afd61","repository",19064309,"tag_last_pulled","tag_last_pushed","tag_status","inactive","v2","tagImages",[],"layerOrdinals","packageName","cveId","sbom","scoutSummary","staticSummary","isScoutPaymentRequired","canSeeVulnerabilities",{"_66":67,"_72":73,"_75":76,"_77":78,"_79":11,"_39":80,"_81":82,"_83":84,"_46":86,"_87":88,"_89":90,"_91":-5,"_92":93,"_94":95,"_96":97,"_98":-5,"_99":93,"_100":101,"_102":11,"_103":88,"_104":105,"_110":11,"_111":112,"_116":88,"_117":118},"categories",[68],{"_46":69,"_70":71},"Monitoring & observability","slug","monitoring-and-observability","content_types",[74,28],"helm","date_registered","2023-01-24T10:50:07.935102Z","description","Bitnami Helm chart for Grafana Tempo","is_private","2025-08-13T20:01:14.766657Z","last_modified","2026-03-19T16:23:10.820755Z","media_types",[85,45],"application/vnd.cncf.helm.config.v1+json","grafana-tempo","namespace","bitnamicharts","pull_count",636521,"repository_type","star_count",0,"status",1,"status_description","active","source","collaborator_count","full_description","\n\n# Bitnami Secure Images Helm chart for Grafana Tempo\n\nGrafana 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.\n\n[Overview of Grafana Tempo](https://github.com/grafana/tempo)\n\nTrademarks: 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.\n\n## TL;DR\n\n```console\nhelm install my-release oci://REGISTRY_NAME/REPOSITORY_NAME/grafana-tempo\n```\n\n> Note: You need to substitute the placeholders `REGISTRY_NAME` and `REPOSITORY_NAME` with a reference to your Helm chart registry and repository.\n\n## Introduction\n\nBitnami 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.\n\nThis chart bootstraps a [Grafana Tempo](https://github.com/grafana/tempo) Deployment in a [Kubernetes](https://kubernetes.io) cluster using the [Helm](https://helm.sh) package manager.\n\n## Before you begin\n\n- Kubernetes 1.23+\n- Helm 3.8.0+\n- PV provisioner support in the underlying infrastructure\n\n## Installing the Chart\n\nTo install the chart with the release name `my-release`:\n\n```console\nhelm install my-release oci://REGISTRY_NAME/REPOSITORY_NAME/grafana-tempo\n```\n\n> Note: You need to substitute the placeholders `REGISTRY_NAME` and `REPOSITORY_NAME` with a reference to your Helm chart registry and repository. For example, in the case of Bitnami, you need to use `REGISTRY_NAME=registry-1.docker.io` and `REPOSITORY_NAME=bitnamicharts`.\n\nThe command deploys grafana-tempo on the Kubernetes cluster in the default configuration. The [Parameters](#parameters) section lists the parameters that can be configured during installation.\n\n> **Tip**: List all releases using `helm list`\n\n## Configuration and installation details\n\nThis section describes credentials, configuration, and other installation options.\n\n### Resource requests and limits\n\nBitnami charts allow setting resource requests and limits for all containers inside the chart deployment. These are inside the `resources` value (check parameter table). Setting requests is essential for production workloads and these should be adapted to your specific use case.\n\nTo make this process easier, the chart contains the `resourcesPreset` values, which automatically sets the `resources` section according to different presets. Check these presets in [the bitnami/common chart](https://github.com/bitnami/charts/blob/main/bitnami/common/templates/_resources.tpl#L15). However, in production workloads using `resourcesPreset` is discouraged as it may not fully adapt to your specific needs. Find more information on container resource management in the [official Kubernetes documentation](https://kubernetes.io/docs/concepts/configuration/manage-resources-containers/).\n\n### [Rolling VS Immutable tags](https://techdocs.broadcom.com/us/en/vmware-tanzu/bitnami-secure-images/bitnami-secure-images/services/bsi-doc/apps-tutorials-understand-rolling-tags-containers-index.html)\n\nIt 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.\n\nBitnami will release a new chart updating its containers if a new version of the main container, significant changes, or critical vulnerabilities exist.\n\n### Prometheus metrics\n\nThis chart can be integrated with Prometheus by setting `metrics.enabled` to true. This will expose the Grafana Tempo native Prometheus port in both the containers and services. The services will also have the necessary annotations to be automatically scraped by Prometheus.\n\n#### Prometheus requirements\n\nIt is necessary to have a working installation of Prometheus or Prometheus Operator for the integration to work. Install the [Bitnami Prometheus helm chart](https://github.com/bitnami/charts/tree/main/bitnami/prometheus) or the [Bitnami Kube Prometheus helm chart](https://github.com/bitnami/charts/tree/main/bitnami/kube-prometheus) to easily have a working Prometheus in your cluster.\n\n#### Integration with Prometheus Operator\n\nThe chart can deploy `ServiceMonitor` objects for integration with Prometheus Operator installations. To do so, set the value `metrics.serviceMonitor.enabled=true`. Ensure that the Prometheus Operator `CustomResourceDefinitions` are installed in the cluster or it will fail with the following error:\n\n```text\nno matches for kind \"ServiceMonitor\" in version \"monitoring.coreos.com/v1\"\n```\n\nInstall the [Bitnami Kube Prometheus helm chart](https://github.com/bitnami/charts/tree/main/bitnami/kube-prometheus) for having the necessary CRDs and the Prometheus Operator.\n\n### Tempo configuration\n\nThe 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](https://grafana.com/docs/tempo/latest/configuration/) for the list of possible configurations.\n\n### Additional environment variables\n\nIn 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`.\n\n```yaml\ncompactor:\n extraEnvVars:\n - name: LOG_LEVEL\n value: error\n\ndistributor:\n extraEnvVars:\n - name: LOG_LEVEL\n value: error\n\ningester:\n extraEnvVars:\n - name: LOG_LEVEL\n value: error\n\nquerier:\n extraEnvVars:\n - name: LOG_LEVEL\n value: error\n\nqueryFrontend:\n extraEnvVars:\n - name: LOG_LEVEL\n value: error\n\nvulture:\n extraEnvVars:\n - name: LOG_LEVEL\n value: error\n```\n\nAlternatively, you can use a ConfigMap or a Secret with the environment variables. To do so, use the `extraEnvVarsCM` or the `extraEnvVarsSecret` values.\n\n### Sidecars\n\nIf 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` .\n\n```yaml\nsidecars:\n- name: your-image-name\n image: your-image\n imagePullPolicy: Always\n ports:\n - name: portname\n containerPort: 1234\n```\n\nIf these sidecars export extra ports, extra port definitions can be added using the `service.extraPorts` parameter (where available), as shown in the example below:\n\n```yaml\nservice:\n extraPorts:\n - name: extraPort\n port: 11311\n targetPort: 11311\n```\n\n> NOTE: This Helm chart already includes sidecar containers for the Prometheus exporters (where applicable). These can be activated by adding the `--enable-metrics=true` parameter at deployment time. The `sidecars` parameter should therefore only be used for any extra sidecar containers.\n\nIf additional init containers are needed in the same pod, they can be defined using the `initContainers` parameter. Here is an example:\n\n```yaml\ninitContainers:\n - name: your-image-name\n image: your-image\n imagePullPolicy: Always\n ports:\n - name: portname\n containerPort: 1234\n```\n\nLearn more about [sidecar containers](https://kubernetes.io/docs/concepts/workloads/pods/) and [init containers](https://kubernetes.io/docs/concepts/workloads/pods/init-containers/).\n\n### Pod affinity\n\nThis chart allows you to set your custom affinity using the `affinity` parameter. Find more information about Pod affinity in the [kubernetes documentation](https://kubernetes.io/docs/concepts/configuration/assign-pod-node/#affinity-and-anti-affinity).\n\nAs an alternative, use one of the preset configurations for pod affinity, pod anti-affinity, and node affinity available at the [bitnami/common](https://github.com/bitnami/charts/tree/main/bitnami/common#affinities) chart. To do so, set the `podAffinityPreset`, `podAntiAffinityPreset`, or `nodeAffinityPreset` parameters inside each of the subsections: `distributor`, `compactor`, `ingester`, `querier`, `queryFrontend` and `vulture`.\n\n### External cache support\n\nYou 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](#parameters). You should also disable the Memcached installation with the `memcached.enabled` option. Here is an example:\n\n```console\nmemcached.enabled=false\nexternalMemcached.host=myexternalhost\nexternalMemcached.port=11211\n```\n\n### Backup and restore\n\nTo back up and restore Helm chart deployments on Kubernetes, you need to back up the persistent volumes from the source deployment and attach them to a new deployment using [Velero](https://velero.io/), a Kubernetes backup/restore tool. Find the instructions for using Velero in [this guide](https://techdocs.broadcom.com/us/en/vmware-tanzu/bitnami-secure-images/bitnami-secure-images/services/bsi-doc/apps-tutorials-backup-restore-deployments-velero-index.html).\n\n### FIPS parameters\n\nThe FIPS parameters only have effect if you are using images from the [Bitnami Secure Images catalog](https://go-vmware.broadcom.com/contact-us).\n\nFor more information on this new support, please refer to the [FIPS Compliance section](https://techdocs.broadcom.com/us/en/vmware-tanzu/bitnami-secure-images/bitnami-secure-images/services/bsi-doc/security-frameworks-FIPS-compliance.html).\n\n### Gateway API\n\nThis chart provides support for exposing Grafana Tempo using the [Gateway API](https://gateway-api.sigs.k8s.io/) and its `HTTPRoute` resource. If you have a Gateway controller installed on your cluster, such as APISIX, Contour, Envoy Gateway, NGINX Gateway Fabric or Kong Ingress Controller you can utilize the Gateway controller to serve your application. To enable Gateway API integration, set `gateway.httpRoute.enabled` to `true`.\nThe Gateway to be used can be customized by setting the `gateway.httpRoute.parentRefs` parameter. By default, it will reference a Gateway named `gateway` in the same namespace as the release.\n\nYou can specify the list of hostnames to be mapped to the deployment using the `gateway.httpRoute.hostnames` parameter. Additionally, you can customize the rules used to route the traffic to the service by modifying the `gateway.httpRoute.matches` and `gateway.httpRoute.filters` parameters or adding new rules using the `gateway.httpRoute.extraRules` parameter.\n\n### Ingress\n\nThis chart provides support for Ingress resources. If you have an ingress controller installed on your cluster, such as NGINX Ingress Controller or Contour you can utilize the ingress controller to serve your application. To enable Ingress integration, set `gateway.ingress.enabled` to `true`.\n\nThe most common scenario is to have one host name mapped to the deployment. In this case, the `gateway.ingress.hostname` property can be used to set the host name. The `gateway.ingress.tls` parameter can be used to add the TLS configuration for this host.\n\nHowever, it is also possible to have more than one host. To facilitate this, the `gateway.ingress.extraHosts` parameter (if available) can be set with the host names specified as an array. The `gateway.ingress.extraTls` parameter (if available) can also be used to add the TLS configuration for extra hosts.\n\n> NOTE: For each host specified in the `gateway.ingress.extraHosts` parameter, it is necessary to set a name, path, and any annotations that the Ingress controller should know about. Not all annotations are supported by all Ingress controllers, but [this annotation reference document](https://github.com/kubernetes/ingress-nginx/blob/master/docs/user-guide/nginx-configuration/annotations.md) lists the annotations supported by many popular Ingress controllers.\n\nAdding the TLS parameter (where available) will cause the chart to generate HTTPS URLs, and the application will be available on port 443. The actual TLS secrets do not have to be generated by this chart. However, if TLS is enabled, the Ingress record will not work until the TLS secret exists.\n\n[Learn more about Ingress controllers](https://kubernetes.io/docs/concepts/services-networking/ingress-controllers/).\n\n## Persistence\n\nThe [Bitnami grafana-tempo](https://github.com/bitnami/containers/tree/main/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.\n\n## Parameters\n\nThe following subsections list global, common, and component-specific parameters.\n\n### Global parameters\n\n| Name | Description | Value |\n| ----------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------ |\n| `global.imageRegistry` | Global Docker image registry | `\"\"` |\n| `global.imagePullSecrets` | Global Docker registry secret names as an array | `[]` |\n| `global.defaultStorageClass` | Global default StorageClass for Persistent Volume(s) | `\"\"` |\n| `global.storageClass` | DEPRECATED: use global.defaultStorageClass instead | `\"\"` |\n| `global.defaultFips` | Default value for the FIPS configuration (allowed values: '', restricted, relaxed, off). Can be overridden by the 'fips' object | `restricted` |\n| `global.security.allowInsecureImages` | Allows skipping image verification | `false` |\n| `global.compatibility.openshift.adaptSecurityContext` | Adapt the securityContext sections of the deployment to make them compatible with Openshift restricted-v2 SCC: remove runAsUser, runAsGroup and fsGroup and let the platform use their allowed default IDs. Possible values: auto (apply if the detected running cluster is Openshift), force (perform the adaptation always), disabled (do not perform adaptation) | `auto` |\n\n### Common parameters\n\n| Name | Description | Value |\n| ------------------------ | --------------------------------------------------------------------------------------- | --------------- |\n| `kubeVersion` | Override Kubernetes version | `\"\"` |\n| `nameOverride` | String to partially override common.names.fullname | `\"\"` |\n| `fullnameOverride` | String to fully override common.names.fullname | `\"\"` |\n| `commonLabels` | Labels to add to all deployed objects | `{}` |\n| `commonAnnotations` | Annotations to add to all deployed objects | `{}` |\n| `clusterDomain` | Kubernetes cluster domain name | `cluster.local` |\n| `extraDeploy` | Array of extra objects to deploy with the release | `[]` |\n| `diagnosticMode.enabled` | Enable diagnostic mode (all probes will be disabled and the command will be overridden) | `false` |\n| `diagnosticMode.command` | Command to override all containers in the deployments/statefulsets | `[\"sleep\"]` |\n| `diagnosticMode.args` | Args to override all containers in the deployments/statefulsets | `[\"infinity\"]` |\n\n### Gateway Deployment Parameters\n\n| Name | Description | Value |\n| ----------------------------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ----------------------- |\n| `gateway.enabled` | Enable Gateway deployment | `true` |\n| `gateway.image.registry` | Nginx image registry | `REGISTRY_NAME` |\n| `gateway.image.repository` | Nginx image repository | `REPOSITORY_NAME/nginx` |\n| `gateway.image.digest` | Nginx image digest in the way sha256:aa.... Please note this parameter, if set, will override the tag | `\"\"` |\n| `gateway.image.pullPolicy` | Nginx image pull policy | `IfNotPresent` |\n| `gateway.image.pullSecrets` | Nginx image pull secrets | `[]` |\n| `gateway.image.debug` | Enable debugging in the initialization process | `false` |\n| `gateway.extraEnvVars` | Array with extra environment variables to add to gateway nodes | `[]` |\n| `gateway.extraEnvVarsCM` | Name of existing ConfigMap containing extra env vars for gateway nodes | `\"\"` |\n| `gateway.extraEnvVarsSecret` | Name of existing Secret containing extra env vars for gateway nodes | `\"\"` |\n| `gateway.command` | Override default container command (useful when using custom images) | `[]` |\n| `gateway.args` | Override default container args (useful when using custom images) | `[]` |\n| `gateway.extraArgs` | Additional container args (will be concatenated to args, unless diagnosticMode is enabled) | `[]` |\n| `gateway.verboseLogging` | Show the gateway access_log | `false` |\n| `gateway.replicaCount` | Number of Gateway replicas to deploy | \n\n_Note: the README for this chart is longer than the DockerHub length limit of 25000, so it has been trimmed. The full README can be found at https://techdocs.broadcom.com/us/en/vmware-tanzu/bitnami-secure-images/bitnami-secure-images/services/bsi-app-doc/apps-charts-grafana-tempo-index.html_","has_starred","hub_user","immutable_tags_settings",{"_106":11,"_107":108},"enabled","rules",[109],".*","is_automated","permissions",{"_113":17,"_114":11,"_115":11},"read","write","admin","user","storage_size",13466651,"isOrg","reponame","tag","canDeleteTags","isHubSbxKitsEnabled","currentTab","","tagAttestations","displaySecurityMetadata","showSbxLogoOverride","routes/_layout.layers.$namespace.$reponame.$tag.(images).($imageUrlDigest)._index",{"_23":24,"_59":-7,"_57":-7,"_58":-7,"_25":131,"_31":32,"_133":-7,"_134":11},{"_27":28,"_29":30,"_31":32,"_33":34,"_35":36,"_37":132,"_39":40,"_41":30,"_42":43,"_44":45,"_46":47,"_48":49,"_50":-5,"_51":40,"_52":53,"_54":17},[],"imageWithLayers","hasPermissionToViewRepoSettings","actionData","errors"]

bitnamicharts/grafana-tempo:sha256-77ad745045e2d15212fb727bb3d2da4022bc9902aacd0b170ba1b513b07afd61