[{"_1":2,"_139":-5,"_140":-5},"loaderData",{"_3":4,"_17":18,"_25":26,"_133":134},"root",{"_5":-5,"_6":-7,"_7":8,"_9":-7,"_10":11,"_12":-7,"_13":14,"_15":16},"currentUser","primaryEmail","siteVerification","6LeIxAcTAAAAAJcZVRqyHh71UMIEGNQ_MXjiZKhI","toast","enableDev",false,"incidentStatus","theme","system","contrast","normal","routes/_layout",{"_19":-5,"_20":21,"_22":21,"_23":11,"_24":21},"username","isAskGordonEnabled",true,"isUsingNewTemplate","showMinimalLanding","showHoneypotTrap","routes/_layout.layers.$namespace.$reponame.$tag.(images).($imageUrlDigest)",{"_27":28,"_29":30,"_59":60,"_61":-7,"_62":-7,"_63":-7,"_64":-7,"_65":-5,"_66":-5,"_67":11,"_68":11,"_52":69,"_123":21,"_91":92,"_124":90,"_125":51,"_35":36,"_126":11,"_127":21,"_128":129,"_130":-5,"_131":11,"_132":11},"scanningType","none","tagData",{"_31":32,"_33":34,"_35":36,"_37":38,"_39":40,"_41":42,"_43":44,"_45":34,"_46":47,"_48":49,"_50":51,"_52":53,"_54":-5,"_55":44,"_56":57,"_58":21},"content_type","image","creator",35095401,"digest","sha256:1053d122bcdac5133697bfe58a6fa0e0b68b348387f9090c4e4d220de1ae260d","full_size",7947,"id",924240125,"images",[],"last_updated","2025-06-26T23:20:55.179862Z","last_updater","last_updater_username","bitnamibot508","media_type","application/vnd.oci.image.index.v1+json","name","sha256-3bfc2e9472f360707a7a054984ccc13734231b48339df48c0451620ee3d36c4a","repository",25061103,"tag_last_pulled","tag_last_pushed","tag_status","inactive","v2","tagImages",[],"layerOrdinals","packageName","cveId","sbom","scoutSummary","staticSummary","isScoutPaymentRequired","canSeeVulnerabilities",{"_70":71,"_76":77,"_79":80,"_81":82,"_83":11,"_43":84,"_85":86,"_87":88,"_50":90,"_91":92,"_93":94,"_95":-5,"_96":97,"_98":99,"_100":101,"_102":-5,"_103":97,"_104":105,"_106":11,"_107":92,"_108":109,"_114":11,"_115":116,"_120":92,"_121":122},"categories",[72],{"_50":73,"_74":75},"Monitoring & observability","slug","monitoring-and-observability","content_types",[78,32],"helm","date_registered","2024-09-06T10:36:25.655398Z","description","Bitnami Helm chart for Zipkin","is_private","2025-08-11T12:34:53.705268Z","last_modified","2026-03-16T14:25:42.523774Z","media_types",[89,49],"application/vnd.cncf.helm.config.v1+json","zipkin","namespace","bitnamicharts","pull_count",351894,"repository_type","star_count",0,"status",1,"status_description","active","source","collaborator_count","full_description","\n\n# Bitnami Secure Images Helm chart for Zipkin\n\nZipkin is a distributed tracing system that helps collect and analyze timing data to troubleshoot latency issues in service architectures, providing visibility into service call performance.\n\n[Overview of Zipkin](https://zipkin.io/)\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/zipkin\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\nThis chart bootstraps a [zipkin](https://github.com/bitnami/containers/tree/main/bitnami/zipkin) deployment on 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\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/zipkin\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 zipkin 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## Uninstalling the Chart\n\nTo uninstall/delete the `my-release` deployment:\n\n```console\nhelm delete my-release\n```\n\nThe command removes all the Kubernetes components associated with the chart and deletes the release.\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### 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### 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### Prometheus metrics\n\nThis chart can be integrated with Prometheus by setting `metrics.enabled` to `true`. This will expose Zipkin native Prometheus endpoint in the service. It will 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### Zipkin application properties\n\nThe chart supports setting zipkin [environment variables](https://github.com/openzipkin/zipkin/blob/master/zipkin-server/README.md#configuration) via two parameters:\n\n- `configOverrides`: Overrides non-sensitive application properties, such as `QUERY_TIMEOUT`.\n- `secretConfigOverrides`: Overrides sensitive application properties, such as `MYSQL_PASSWORD`.\n\nIn the following example, we use `configOverrides` to disable the zipkin UI:\n\n```yaml\nconfigOverrides:\n UI_ENABLED: false\n```\n\nAlternatively, it is possible to use an external configmap and an external secret for this configuration: `existingConfigmap` and `existingSecret`.\n\n> NOTE: Configuration overrides take precedence over the chart values. For example, setting `QUERY_PORT` via `configOverrides` leaves the `containerPorts.http` without effect.\n\n### Using collectors\n\nThe Bitnami Zipkin image includes all the [available collectors](https://github.com/openzipkin/zipkin/tree/master/zipkin-collector). These can be configured using the `configOverrides` and `secretConfigOverrides` values. By default, it is using the HTTP collector endpoint.\n\nIn the examples below, we enable other collectors:\n\n#### Using Bitnami RabbitMQ helm chart as collector\n\nIn the following example we will install the Bitnami RabbitMQ helm chart and [configure zipkin](https://github.com/openzipkin/zipkin/tree/master/zipkin-collector/rabbitmq) to use it as storage. Replace the RABBITMQ_USER and RABBITMQ_PASSWORD placeholders.\n\n```bash\nhelm install rabbitmq oci://REGISTRY_NAME/REPOSITORY_NAME/rabbitmq --set auth.username=RABBITMQ_USER --set auth.password=RABBITMQ_PASSWORD\n```\n\nThen install the zipkin helm chart with the following values:\n\n```yaml\n#\n# Example with RabbitMQ\n#\n# This section goes to a ConfigMap\nconfigOverrides:\n RABBIT_ADDRESSES: rabbitmq\n RABBIT_USER: RABBITMQ_USER\n# This section goes to a Secret\nsecretConfigOverrides:\n RABBIT_PASSWORD: RABBITMQ_PASSWORD\n```\n\n#### Using Bitnami Kafka helm chart as collector\n\nIn the following example we will install the Bitnami Kafka helm chart and [configure zipkin](https://github.com/openzipkin/zipkin/tree/master/zipkin-collector/kafka) to use it as storage.\n\n```bash\nhelm install kafka oci://REGISTRY_NAME/REPOSITORY_NAME/kafka\n```\n\nThen install the zipkin helm chart with the following values:\n\n```yaml\n#\n# Example with RabbitMQ\n#\n# This section goes to a ConfigMap\nconfigOverrides:\n COLLECTOR_KAFKA_ENABLED: true\n KAFKA_BOOTSTRAP_SERVERS: kafka:9092\n```\n\n### Supported storage types\n\nThis chart natively supports the following storage methods:\n\n- Cassandra: Set `storageType=cassandra3`. If using embedded Cassandra subchart set `cassandra.enabled=true`. If using an external Cassandra set the `cassandra.enabled=false` and the `externalDatabase` section (see corresponding section).\n- In memory storage: Set `storageType=mem`.\n\nIt is possible to configure the rest of storage backends by setting `storageType=other`, and using the `configOverrides` and `secretConfigOverrides` values. Set the proper [environment variables](https://github.com/openzipkin/zipkin/blob/master/zipkin-server/README.md#configuration). In the following sections we show two examples:\n\n#### Using Bitnami Elasticsearch helm chart as storage\n\nIn the following example we will install the Bitnami Elasticsearch helm chart and configure zipkin to use it as storage.\n\n```bash\nhelm install elasticsearch oci://REGISTRY_NAME/REPOSITORY_NAME/elasticsearch\n```\n\nThen install the zipkin helm chart with the following values:\n\n```yaml\n#\n# Example with Elasticsearch\n#\nstorageType: other\n# This section goes to a ConfigMap\nconfigOverrides:\n STORAGE_TYPE: elasticsearch\n ES_HOSTS: http://elasticsearch:9200\ncassandra:\n enabled: false\n```\n\n#### Using Bitnami MySQL helm chart as storage\n\nIn the following example we will install the Bitnami MySQL helm chart and configure zipkin to use it as storage. Replace the DB_USER, DB_DATABASE and DB_PASSWORD placeholders.\n\n```bash\nhelm install mysql oci://REGISTRY_NAME/REPOSITORY_NAME/mysql --set auth.usernames=DB_USER --set auth.password=DB_PASSWORD --set auth.database=DB_DATABASE\n```\n\nThen install the zipkin helm chart with the following values:\n\n```yaml\n#\n# Example with MongoDB\n#\nstorageType: other\n# This section goes to a ConfigMap\nconfigOverrides:\n STORAGE_TYPE: mysql\n MYSQL_DB: DB_DATABASE\n MYSQL_HOST: mysql\n MYSQL_TCP_PORT: 3306\n MYSQL_USER: DB_USER\n# This section goes to a Secret\nsecretConfigOverrides:\n MYSQL_PASSWORD: DB_PASSWORD\ncassandra:\n enabled: false\n```\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.\n\n```yaml\nextraEnvVars:\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 zipkin (such as additional metrics or logging exporters), they can be defined using the `sidecars` parameter.\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 server:\n extraPorts:\n - name: extraPort\n port: 11311\n targetPort: 11311\n```\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.\n\n### Deploying extra resources\n\nThere are cases where you may want to deploy extra objects, such a ConfigMap containing your app's configuration or some extra deployment with a micro service used by your app. For covering this case, the chart allows adding the full specification of other objects using the `extraDeploy` parameter.\n\n### Gateway API\n\nThis chart provides support for exposing Zipkin 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 `httpRoute.enabled` to `true`.\nThe Gateway to be used can be customized by setting the `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 `httpRoute.hostnames` parameter. Additionally, you can customize the rules used to route the traffic to the service by modifying the `httpRoute.matches` and `httpRoute.filters` parameters or adding new rules using the `httpRoute.extraRules` parameter.\n\nThis chart also supports creating a `BackendTLSPolicy` to define the SNI the Gateway should use to connect to the Zipkin backend pods and how the certificate served by these pods should be verified. To do so, set the `backendTLSPolicy.enabled` parameter to `true`. Please note it's required to secure traffic using TLS as explained in the [Securing traffic using TLS](#securing-traffic-using-tls) section to be able to use this feature.\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](https://github.com/bitnami/charts/tree/main/bitnami/nginx-ingress-controller) or [contour](https://github.com/bitnami/charts/tree/main/bitnami/contour) you can utilize the ingress controller to serve your application. To enable Ingress integration, set `ingress.enabled` to `true`.\n\nThe most common scenario is to have one host name mapped to the deployment. In this case, the `ingress.hostname` property can be used to set the host name. The `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 `ingress.extraHosts` parameter (if available) can be set with the host names specified as an array. The `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 `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### Securing traffic using TLS\n\nBy default, this chart assumes TLS is managed by the Ingress Controller and terminates the TLS connection in the Ingress Controller. This can be done by setting `ingress.enabled` and `ingress.tls` parameters to `true` as explained in the section above. However, it is possible to configure TLS encryption for Zipkin directly by setting `tls.enabled` parameter to `true`.\n\nIt is necessary to create a secret containing the TLS certificates and pass it to the chart via the `tls.existingSecret` parameter. The secret should contain a `tls.crt` and `tls.key` keys including the certificate and key files respectively.\n\nYou can manually create the required TLS certificates or relying on the chart auto-generation capabilities. The chart supports two different ways to auto-generate the required certificates:\n\n- Using Helm capabilities. Enable this feature by setting `tls.autoGenerated.enabled` to `true` and `tls.autoGenerated.engine` to `helm`.\n- Relying on CertManager (please note it's required to have CertManager installed in your K8s cluster). Enable this feature by setting `tls.autoGenerated.enabled` to `true` and `tls.autoGenerated.engine` to `cert-manager`. Please note it's supported to use an existing Issuer/ClusterIssuer for issuing the TLS certificates by setting the `tls.autoGenerated.certManager.existingIssuer` and `tls.autoGenerated.certManager.existingIssuerKind` parameters.\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.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| `apiVersions` | Override Kubernetes API versions reported by .Capabilities | `[]` |\n| `nameOverride` | String to partially override common.names.name | `\"\"` |\n| `fullnameOverride` | String to fully override common.names.fullname | `\"\"` |\n| `namespaceOverride` | String to fully override common.names.namespace | `\"\"` |\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.loc\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-zipkin-index.html_","has_starred","hub_user","immutable_tags_settings",{"_110":11,"_111":112},"enabled","rules",[113],".*","is_automated","permissions",{"_117":21,"_118":11,"_119":11},"read","write","admin","user","storage_size",3009396,"isOrg","reponame","tag","canDeleteTags","isHubSbxKitsEnabled","currentTab","","tagAttestations","displaySecurityMetadata","showSbxLogoOverride","routes/_layout.layers.$namespace.$reponame.$tag.(images).($imageUrlDigest)._index",{"_27":28,"_63":-7,"_61":-7,"_62":-7,"_29":135,"_35":36,"_137":-7,"_138":11},{"_31":32,"_33":34,"_35":36,"_37":38,"_39":40,"_41":136,"_43":44,"_45":34,"_46":47,"_48":49,"_50":51,"_52":53,"_54":-5,"_55":44,"_56":57,"_58":21},[],"imageWithLayers","hasPermissionToViewRepoSettings","actionData","errors"]

bitnamicharts/zipkin:sha256-3bfc2e9472f360707a7a054984ccc13734231b48339df48c0451620ee3d36c4a