Install Redis Enterprise Helm chart

Install Redis Enterprise for Kubernetes version 7.8.6 using Helm charts.

Helm 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/.

Prerequisites

• A supported distribution of Kubernetes.
• At least three worker nodes.
• Kubernetes client (kubectl).
• Helm 3.10 or later or 3.18 for migrating from a non-Helm installation.

If you suspect your file descriptor limits are below 100,000, you must either manually increase limits or Allow automatic resource adjustment. Most major cloud providers and standard container runtime configurations set default file descriptor limits well above the minimum required by Redis Enterprise. In these environments, you can safely run without enabling automatic resource adjustment.

Example values

The steps below use the following placeholders to indicate command line parameters you must provide:

• <repo-name> is the name of the repo holding your Helm chart (example: redis).
• <release-name> is the name you give a specific installation of the Helm chart (example: my-redis-enterprise-operator)
• <chart-version> is the version of the Helm chart you are installing (example: 7.8.2-2)
• <namespace-name> is the name of the new namespace the Redis operator will run in (example: ns1)
• <path-to-chart> is the filepath to the Helm chart, if it is stored in a local directory (example: /home/charts/redis-enterprise-operator)

Install

1. Add the Redis repository.

   helm repo add <repo-name> https://helm.redis.io/
   

2. Install the Helm chart into a new namespace.

helm install <release-name> <repo-name>/redis-enterprise-operator \
    --version <chart-version> \
    --namespace <namespace-name> \
    --create-namespace

To install with Openshift, add --set openshift.mode=true.

To monitor the installation add the --debug flag. The installation runs several jobs synchronously and may take a few minutes to complete.

Install from local directory

1. Find the latest release on the redis-enterprise-k8s-docs repo and download the tar.gz source code into a local directory.

2. Install the Helm chart from your local directory.

helm install <release-name> <path-to-chart> \
    --namespace <namespace-name> \
    --create-namespace

To install with Openshift, add --set openshift.mode=true.

To monitor the installation add the --debug flag. The installation runs several jobs synchronously and may take a few minutes to complete.

Specify values during install

1. View configurable values with helm show values <repo-name>/redis-enterprise-operator.

2. Install the Helm chart, overriding specific value defaults using --set.

helm install <operator-name> <repo-name>/redis-enterprise-operator \
    --version <chart-version> \
    --namespace <namespace-name> \
    --create-namespace
    --set <key1>=<value1> \
    --set <key2>=<value2>

Install with values file

1. View configurable values with helm show values <repo-name>/redis-enterprise-operator.

2. Create a YAML file to specify the values you want to configure.

3. Install the chart with the --values option.

helm install <operator-name> <repo-name>/redis-enterprise-operator \
    --version <chart-version> \
    --namespace <namespace-name> \
    --create-namespace \
    --values <path-to-values-file>

Migrate from a non-Helm installation

To migrate an existing non-Helm installation of the Redis Enterprise operator to a Helm-based installation:

1. Upgrade your existing Redis Enterprise operator to match the version of the Helm chart you want to install. Use the same non-Helm method you used for the original installation.

2. Install the Helm chart adding the --take-ownership flag:

   helm install <release-name> <repo-name>/redis-enterprise-operator --take-ownership
   

   • The --take-ownership flag is available with Helm versions 3.18 or later.
   • This flag is only needed for the first installation of the chart. Subsequent upgrades don't require this flag.
   • Use the helm install command, not helm upgrade.

3. Delete the old ValidatingWebhookConfiguration object from the previous non-Helm installation:

   kubectl delete validatingwebhookconfiguration redis-enterprise-admission
   

   This step is only needed when the admission.limitToNamespace chart value is set to true (the default). In this case, the webhook object installed by the chart is named redis-enterprise-admission-<namespace>, and the original webhook object, named redis-enterprise-admission, becomes redundant. If admission.limitToNamespace is set to false, the webhook installed by the chart is named redis-enterprise-admission, and the existing webhook object is reused.

Upgrade the chart

To upgrade an existing Helm chart installation:

helm upgrade <release-name> <repo-name>/redis-enterprise-operator --version <chart-version>

You can also upgrade from a local directory:

helm upgrade <release-name> <path-to-chart>

For example, to upgrade a chart with the release name my-redis-enterprise from the chart's root directory:

helm upgrade my-redis-enterprise .

To upgrade with OpenShift, add --set openshift.mode=true.

The upgrade process automatically updates the operator and its components, including the Custom Resource Definitions (CRDs). The CRDs are versioned and update only if the new version is higher than the existing version.

After you upgrade the operator, you might need to upgrade your Redis Enterprise clusters, depending on the Redis software version bundled with the operator. For detailed information about the upgrade process, see Redis Enterprise for Kubernetes upgrade documentation.

For more information and options when upgrading charts, see helm upgrade.

Uninstall

1. Delete any custom resources managed by the operator. See Delete custom resources for detailed steps. You must delete custom resources in the correct order to avoid errors.

2. Uninstall the Helm chart.

helm uninstall <release-name>

This removes all Kubernetes resources associated with the chart and deletes the release.

Known limitations

• The steps for creating the RedisEnterpriseCluster (REC) and other custom resources remain the same.
• The chart doesn't include configuration options for multiple namespaces, rack-awareness, and Vault integration. The steps for configuring these options remain the same.
• The chart has had limited testing in advanced setups, including Active-Active configurations, air-gapped deployments, and IPv6/dual-stack environments.