{
  "schema_version": 2,
  "id": "operate/kubernetes/deployment/helm",
  "title": "Install Redis Enterprise Helm chart",
  "url": "https://redis.io/docs/latest/operate/kubernetes/7.8.6/deployment/helm/",
  "summary": "Install Redis Enterprise for Kubernetes version 7.8.6 using Helm charts.",
  "content": "\nHelm charts provide a simple way to install the Redis Enterprise for Kubernetes operator in just a few steps. For more information about Helm, go to [https://helm.sh/docs/](https://helm.sh/docs/).\n\n\u003e [!NOTE]\n\u003e  This feature is currently in public preview and is not supported on production workloads. Only new installations of the Redis operator are supported at this time. The steps for [creating the RedisEnterpriseCluster (REC)](https://redis.io/docs/latest/operate/kubernetes/deployment/quick-start#create-a-redis-enterprise-cluster-rec) and other custom resources remain the same.\n\n## Prerequisites\n\n- A [supported distribution](https://redis.io/docs/latest/operate/kubernetes/reference/supported_k8s_distributions) of Kubernetes.\n- At least three worker nodes.\n- [Kubernetes client (kubectl)](https://kubernetes.io/docs/tasks/tools/).\n- [Helm 3.10 or later](https://helm.sh/docs/intro/install/).\n\n### Example values\n\nThe steps below use the following placeholders to indicate command line parameters you must provide:\n\n- `\u003crelease-name\u003e` is the name you give a specific installation of the Helm chart (example: `my-redis-enterprise-operator`)\n- `\u003cchart-version\u003e` is the version of the Helm chart you are installing (example: `7.8.2-2`)\n- `\u003cnamespace-name\u003e` is the name of the new namespace the Redis operator will run in (example: `ns1`)\n- `\u003cpath-to-chart\u003e` is the filepath to the Helm chart, if it is stored in a local directory (example: `/home/charts/redis-enterprise-operator`)\n\n## Install\n\n1. Add the Redis repository.\n\n```sh\nhelm repo add redis https://helm.redis.io\n```\n\n2. Install the Helm chart into a new namespace.\n\n```sh\nhelm install \u003crelease-name\u003e redis/redis-enterprise-operator \\\n    --version \u003cchart-version\u003e \\\n    --namespace \u003cnamespace-name\u003e \\\n    --create-namespace\n```\n\nTo install with Openshift, add `--set openshift.mode=true`.\n\nTo monitor the installation add the `--debug` flag. The installation runs several jobs synchronously and may take a few minutes to complete.\n\n### Install from local directory\n\nIf you need a local copy of the chart, for example to inspect it or customize values, use one of the following methods.\n\n**Pull the packaged chart (recommended).** `helm pull` fetches the exact packaged chart the Helm repository serves for the version you specify, matching what `helm install` from the repository would deploy.\n\n1. Add the Redis repository, if you haven't already.\n\n   ```sh\n   helm repo add \u003crepo-name\u003e https://helm.redis.io\n   ```\n\n2. Pull and unpack the chart. This creates a `redis-enterprise-operator` directory in your current location.\n\n   ```sh\n   helm pull \u003crepo-name\u003e/redis-enterprise-operator --version \u003cchart-version\u003e --untar\n   ```\n\n3. Install the Helm chart from the local directory.\n\n   ```sh\n   helm install \u003crelease-name\u003e ./redis-enterprise-operator \\\n       --namespace \u003cnamespace-name\u003e \\\n       --create-namespace\n   ```\n\n**Download the source code.** Alternatively, download the chart source from GitHub.\n\n1. Find the latest release on the [redis-enterprise-k8s-docs](https://github.com/RedisLabs/redis-enterprise-k8s-docs/releases) repo and download the `tar.gz` source code into a local directory.\n\n2. Install the Helm chart from your local directory.\n\n   ```sh\n   helm install \u003crelease-name\u003e \u003cpath-to-chart\u003e \\\n       --namespace \u003cnamespace-name\u003e \\\n       --create-namespace\n   ```\n\nTo install with Openshift, add `--set openshift.mode=true`.\n\nTo monitor the installation add the `--debug` flag. The installation runs several jobs synchronously and may take a few minutes to complete.\n\n### Specify values during install\n\n1. View configurable values with `helm show values redis/\u003cchart-name\u003e`.\n\n2. Install the Helm chart, overriding specific value defaults using `--set`.\n\n```sh\nhelm install \u003coperator-name\u003e redis/redis-enterprise-operator \\\n    --version \u003crelease-name\u003e \\\n    --namespace \u003cnamespace-name\u003e \\\n    --create-namespace\n    --set \u003ckey1\u003e=\u003cvalue1\u003e \\\n    --set \u003ckey2\u003e=\u003cvalue2\u003e\n```\n\n### Install with values file\n\n1. View configurable values with `helm show values redis/\u003cchart-name\u003e`.\n\n2. Create a YAML file to specify the values you want to configure.\n\n3. Install the chart with the `--values` option.\n\n```sh\nhelm install \u003coperator-name\u003e redis/redis-enterprise-operator \\\n    --version \u003crelease-name\u003e \\\n    --namespace \u003cnamespace-name\u003e \\\n    --create-namespace \\\n    --values \u003cpath-to-values-file\u003e\n```\n\n## Uninstall\n\n1. Delete any custom resources managed by the operator. See [Delete custom resources](https://redis.io/docs/latest/operate/kubernetes/re-clusters/delete-custom-resources) for detailed steps. You must delete custom resources in the correct order to avoid errors.\n\n2. Uninstall the Helm chart.\n\n```sh\nhelm uninstall \u003crelease-name\u003e\n```\n\nThis removes all Kubernetes resources associated with the chart and deletes the release.\n\n\u003e [!NOTE]\n\u003e Custom Resource Definitions (CRDs) installed by the chart are not removed during chart uninstallation. To remove them manually after uninstalling the chart, run `kubectl delete crds -l app=redis-enterprise`.\n\n## Known limitations\n\n- Only new installations of the Redis operator are supported at this time. The steps for [creating the RedisEnterpriseCluster (REC)](https://redis.io/docs/latest/operate/kubernetes/deployment/quick-start#create-a-redis-enterprise-cluster-rec) and other custom resources remain the same.\n- Upgrades and migrations are not supported.\n- The chart doesn't include configuration options for multiple namespaces, rack-awareness, and Vault integration. The steps for configuring these options remain the same.\n- The chart has had limited testing in advanced setups, including Active-Active configurations, air-gapped deployments, and IPv6/dual-stack environments.\n",
  "tags": ["docs","operate","kubernetes"],
  "last_updated": "2026-10-22T06:20:54-07:00"
}