{
  "id": "openshift-operatorhub",
  "title": "Deploy Redis Enterprise with OpenShift OperatorHub",
  "url": "https://redis.io/docs/latest/operate/kubernetes/7.8.4/deployment/openshift/openshift-operatorhub/",
  "summary": "OpenShift provides the OperatorHub where you can install the Redis Enterprise operator from the administrator user interface.",
  "content": "\nYou can deploy Redis Enterprise for Kubernetes from the Red Hat OpenShift CLI. You can also use a UI, [OperatorHub](https://docs.openshift.com/container-platform/4.11/operators/index.html) (Red Hat) to install operators and create custom resources.\n\nTo see which version of Redis Enterprise for Kubernetes supports your OpenShift version, see [Supported Kubernetes distributions]().\n\n## Install the Redis Enterprise operator\n\n If using version 6.2.18-41 or earlier, [Install the security context constraint](#install-security-context-constraint) before installing the operator. \n\n1. Select **Operators \u003e OperatorHub**.\n\n2. Search for _Redis Enterprise_ in the search dialog and select the **Redis Enterprise Operator provided by Redis** marked as **Certified**.\n\n    By default, the image is pulled from Red Hat's registry.\n\n3. On the **Install Operator** page, specify the namespace for the operator.\n\n    Only one namespace per operator is supported.\n\n4. Update the **channel** with the version you're installing.\n\n    For more information about specific versions, see the [release notes]().\n\n5. Choose an approval strategy.\n\n    Use **Manual** for production systems to ensure the operator is only upgraded by approval.\n\n6. Select **Install** and approve the install plan.\n\n   You can monitor the subscription status in **Operators \u003e Installed Operators**.\n\nDO NOT modify or delete the StatefulSet created during the deployment process. Doing so could destroy your Redis Enterprise cluster (REC).\n\n## Install security context constraint\n\nThe Redis Enterprise pods must run in OpenShift with privileges set in a [Security Context Constraint](https://docs.openshift.com/container-platform/4.4/authentication/managing-security-context-constraints.html#security-context-constraints-about_configuring-internal-oauth). This grants the pod various rights, such as the ability to change system limits or run as a particular user.\n\n\n Before creating any clusters, install the security context constraint (SCC) for the operator in [scc.yaml](https://github.com/RedisLabs/redis-enterprise-k8s-docs/blob/master/openshift/scc.yaml).\n\n\nYou only need to install the SCC once, but you must not delete it.\n\n1. Select the project you'll be using or create a new project.\n\n1. Download [`scc.yaml`](https://github.com/RedisLabs/redis-enterprise-k8s-docs/blob/master/openshift/scc.yaml).\n\n1. Apply the file to install the security context constraint.\n\n  ```sh\n  oc apply -f scc.yaml\n  ```\n\nAfter the install, the OperatorHub automatically uses the constraint for Redis Enterprise node pods.\n\n\nIf you are using the recommended RedisEnterpriseCluster name of `rec`, the SCC is automatically bound to the RedisEnterpriseCluster after install.\n\nIf you choose a different name for the RedisEnterpriseCluster, or override the default service account name, you must manually bind the SCC to the RedisEnterpriseCluster’s service account:\n\n  ```sh\n  oc adm policy add-scc-to-user redis-enterprise-scc-v2 \\\n  system:serviceaccount:\u003cmy-project\u003e:\u003crec-service-account-name\u003e\n  ```\n\n\n\n## Create Redis Enterprise custom resources\n\nThe **Installed Operators**-\u003e**Operator details** page shows the provided APIs: **RedisEnterpriseCluster** and **RedisEnterpriseDatabase**. You can select **Create instance** to create custom resources using the OperatorHub interface.\n\nUse the YAML view to create a custom resource file or let OperatorHub generate the YAML file for you by specifying your configuration options in the form view.\n\n\u003cnote\u003e The REC name cannot be changed after cluster creation.\u003c/note\u003e\n\n In versions 6.4.2-4 and 6.4.2-5, REC creation might fail when using the form view due to an error related to the cluster level LDAP. To avoid this, use the YAML view.\n\n\nFor more information on creating and maintaining Redis Enterprise custom resources, see [Redis Enterprise clusters (REC)]() and [Redis Enterprise databases (REDB)]().\n",
  "tags": ["docs","operate","kubernetes"],
  "last_updated": "2026-04-08T12:21:52-07:00"
}