Deployment on Docs

Deploy Redis Enterprise Software for Kubernetes

Mon, 01 Jan 0001 00:00:00 +0000

To deploy Redis Enterprise Software for Kubernetes and start your Redis Enterprise cluster (REC), you need to do the following:

Create a new namespace in your Kubernetes cluster.
Download the operator bundle.
Apply the operator bundle and verify it's running.
Create a Redis Enterprise cluster (REC).

This guide works with most supported Kubernetes distributions. If you're using OpenShift, see Redis Enterprise on OpenShift. For details on what is currently supported, see supported distributions.

Install Redis Enterprise Helm chart

Mon, 01 Jan 0001 00:00:00 +0000

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.

Use a private registry for container images

Mon, 01 Jan 0001 00:00:00 +0000

Redis Enterprise Software, its Kubernetes operator, and the Service Rigger are all distributed as separate container images. Your Kubernetes deployment will pull these images as needed. You can control where these images are pulled from within the operator deployment and also via the Redis Enterprise custom resources.

The operator image also includes the admission controller, which runs as part of the operator container and provides validation for Redis Enterprise database resources.