[{"_1":2,"_134":-5,"_135":-5},"loaderData",{"_3":4,"_13":14,"_21":22,"_128":129},"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},"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:ea21181293d9be7f24118f584c435f912c2e812a3b49ee53fc7532989eac1244","full_size",7947,"id",950991641,"images",[],"last_updated","2025-08-09T02:24:36.836541Z","last_updater","last_updater_username","bitnamibot508","media_type","application/vnd.oci.image.index.v1+json","name","sha256-f766861351fbfe18cc5ea443892c214d0da02011bf7a446bdc286f973bf6f025","repository",24988084,"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":93,"_95":96,"_97":-5,"_98":99,"_100":101,"_102":11,"_103":88,"_104":105,"_110":11,"_111":112,"_116":88,"_117":118},"categories",[68],{"_46":69,"_70":71},"Databases & storage","slug","databases-and-storage","content_types",[74,28],"helm","date_registered","2024-08-28T09:41:04.024632Z","description","Bitnami Helm chart for KeyDB","is_private","2025-08-23T08:21:35.725442Z","last_modified","2026-03-16T14:24:06.182104Z","media_types",[85,45],"application/vnd.cncf.helm.config.v1+json","keydb","namespace","bitnamicharts","pull_count",1121399,"repository_type","star_count",1,"status","status_description","active","source","collaborator_count",0,"full_description","\n\n# Bitnami Secure Images Helm chart for KeyDB\n\nKeyDB is a high performance fork of Redis with a focus on multithreading, memory efficiency, and high throughput.\n\n[Overview of KeyDB](https://github.com/Snapchat/KeyDB)\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/keydb\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 [KeyDB](https://github.com/Snapchat/KeyDB) 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/keydb\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 KeyDB 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### Cluster topologies\n\n#### Default: Master - Replicas\n\nWhen installing the chart with `architecture=replication`, it will deploy a KeyDB Master statefulset and a KeyDB Replica statefulset. The master is responsible for all write operations, while the replicas replicate the write operations from the master and serve read operations. Two services will be exposed:\n\n- KeyDB Master service: Points to the master, where read-write operations can be performed\n- KeyDB Replicas service: Points to the replicas, where only read operations are allowed by default.\n\nIn case the master crashes, the replicas will wait until the master node is respawned again by the Kubernetes Controller Manager.\n\n#### Active Replicas\n\nSimilar to the Master-Replicas architecture, but with the ability to perform read and write operations on the replicas. This is achieved by setting `replica.activeReplica=true`. Find more information about how this mechanism works at the [KeyDB documentation](https://docs.keydb.dev/docs/active-rep).\n\n#### Standalone\n\nWhen installing the chart with `architecture=standalone`, it will deploy a standalone KeyDB Master statefulset. A single service will be exposed:\n\n- KeyDB Master service: Points to the master, where read-write operations can be performed\n\n#### Multi Master - Replicas\n\nSimilar to the Master-Replicas architecture, this architectures deploys both a KeyDB Master statefulset and a KeyDB Replica statefulset. However, in this architecture N Master replicas can be deployed, and KeyDB replicas are configured to follow multiple masters. This can be achieved by setting `master.replicaCount` to a value greater than 1 and setting `replica.activeReplica=true` (please note active replication is mandatory when using multi-master).\n\nFind more information about how this mechanism works at the [KeyDB documentation](https://docs.keydb.dev/docs/multi-master).\n\n### Prometheus metrics\n\nThis chart can be integrated with Prometheus by setting `metrics.enabled` to `true`. This will deploy a sidecar container with [redis_exporter](https://github.com/oliver006/redis_exporter) in all pods and a `metrics` service, which can be configured under the `metrics.service` section. This `metrics` service 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### Update credentials\n\nThe Bitnami KeyDB chart, when upgrading, reuses the secret previously rendered by the chart or the one specified in `auth.existingSecret`. To update credentials, use one of the following:\n\n- Run `helm upgrade` specifying a new password in `auth.password`\n- Run `helm upgrade` specifying a new secret in `auth.existingSecret`\n\n### Using a password file\n\nTo use a password file for KeyDB you need to create a secret containing the password and then deploy the chart using that secret. Follow these instructions:\n\n- Create the secret:\n\n```console\nkubectl create secret generic keydb-password-secret --from-literal=keydb-password=KEYDB_PASSWORD\n```\n\n> Note: the replace the KEYDB_PASSWORD placeholder with the actual password to use.\n\n- Deploy the Helm Chart using the secret name as parameter:\n\n```text\nauth.enabled=true\nauth.existingSecret=keydb-password-secret\nauth.existingSecretPasswordKey=keydb-password\nauth.usePasswordFiles=true\n```\n\n### Securing traffic using TLS\n\nThis chart supports encrypting communications using TLS. To enable this feature, set the `tls.enabled`.\n\nIt is necessary to create a secret containing the TLS certificates and pass it to the chart via the `tls.existingCASecret`, `tls.master.existingSecret` and `tls.replica.existingSecret` (only for replication architecture) parameters. Every secret should contain a `tls.crt` and `tls.key` keys including the certificate and key files respectively. For example: create the CA secret with the certificates files:\n\n```console\nkubectl create secret generic ca-tls-secret --from-file=./tls.crt --from-file=./tls.key\n```\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### Metrics\n\nThe chart optionally can start a metrics exporter for [prometheus](https://prometheus.io). Metrics can be scraped from within the cluster using something similar as the described in the [example Prometheus scrape configuration](https://github.com/prometheus/prometheus/blob/master/documentation/examples/prometheus-kubernetes.yml). If metrics are to be scraped from outside the cluster, the Kubernetes API proxy can be utilized to access the endpoint.\n\nIf you have enabled TLS by specifying `tls.enabled=true` you also need to specify TLS options to the metrics exporter. You can do that via `metrics.extraArgs`. You can find the metrics exporter CLI flags for TLS [here](https://github.com/oliver006/redis_exporter#command-line-flags). For example:\n\nYou can either specify `metrics.extraArgs.skip-tls-verification=true` to skip TLS verification or providing the following values under `metrics.extraArgs` for TLS client authentication:\n\n```console\ntls-client-key-file\ntls-client-cert-file\ntls-ca-cert-file\n```\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### 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### 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\nmaster:\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 KeyDB (such as additional metrics or logging exporters), they can be defined using the `sidecars` parameter.\n\n```yaml\nmaster:\n sidecars:\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\nmaster:\n service:\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 setting the `metrics.enabled` parameter to `true` 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\nmaster:\n initContainers:\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### 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## Persistence\n\nThe [Bitnami KeyDB](https://github.com/bitnami/containers/tree/main/bitnami/keydb) image stores the KeyDB data and configurations at the `/bitnami/keydb/data` path of the container. Persistent Volume Claims are used to keep the data across deployments.\n\nIf you encounter errors when working with persistent volumes, refer to our [troubleshooting guide for persistent volumes](https://docs.bitnami.com/kubernetes/faq/troubleshooting/troubleshooting-persistence-volumes/).\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.keydb.password` | Global KeyDB password (overrides `auth.password`) | `\"\"` |\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.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 chart release | `[\"sleep\"]` |\n| `diagnosticMode.args` | Args to override all containers in the chart release | `[\"infinity\"]` |\n\n### KeyDB Image parameters\n\n| Name | Description | Value |\n| ------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------ | ----------------------- |\n| `image.registry` | KeyDB image registry | `REGISTRY_NAME` |\n| `image.repository` | KeyDB image repository | `REPOSITORY_NAME/keydb` |\n| `image.digest` | KeyDB image digest in the way sha256:aa.... Please note this parameter, if set, will override the tag image tag (immutable tags are recommended) | `\"\"` |\n| `image.pullPolicy` | KeyDB image pull policy | `IfNotPresent` |\n| `image.pullSecrets` | KeyDB image pull secrets | `[]` |\n| `image.debug` | Enable KeyDB image debug mode | `false` |\n\n### KeyDB common configuration parameters\n\n| Name | Description | Value |\n| -------------------------------------------------- | ------------------------------------------------------------------------------------------------------ | ------------- |\n| `architecture` | KeyDB architecture. Allowed values: `standalone` or `replication` | `replication` |\n| `auth.enabled` | Enable password authentication | `true` |\n| `auth.password` | KeyDB password | `\"\"` |\n| `auth.existingSecret` | The name of an existing secret with KeyDB credentials | `\"\"` |\n| `auth.existingSecretPasswordKey` | Password key to be retrieved from existing secret | `\"\"` |\n| `auth.usePasswordFiles` | Mount credentials as files instead of using an environment variable | `true` |\n| `tls.enabled` | Enable TLS communications | `false` |\n| `tls.existingCASecret` | The name of an existing Secret containing the CA certificate for TLS | `\"\"` |\n| `tls.certCAFilename` | The secret key from the existing Secret if 'ca' key is different from the default (ca.crt) | `ca.crt` |\n| `tls.ca` | CA certificate for TLS. Ignored if `tls.existingCASecret` is set | `\"\"` |\n| `tls.master.existingSecret` | The name of an existing Secret containing the TLS certificates for KeyDB master nodes | `\"\"` |\n| `\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-keydb-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",2533548,"isOrg","reponame","tag","canDeleteTags","isHubSbxKitsEnabled","currentTab","","tagAttestations","displaySecurityMetadata","routes/_layout.layers.$namespace.$reponame.$tag.(images).($imageUrlDigest)._index",{"_23":24,"_59":-7,"_57":-7,"_58":-7,"_25":130,"_31":32,"_132":-7,"_133":11},{"_27":28,"_29":30,"_31":32,"_33":34,"_35":36,"_37":131,"_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/keydb:sha256-f766861351fbfe18cc5ea443892c214d0da02011bf7a446bdc286f973bf6f025