Redis Enterprise is supported on OpenShift Kubernetes cluster deployments via an operator. The operator is a software component that runs in your deployment namespace and facilitates deploying and managing Redis Enterprise clusters.

    Quick Start for Kubernetes and OpenShift

    A quick introduction to the steps necessary to get a Redis Enterprise cluster installed in your OpenShift Kubernetes cluster

    Getting Started for 4.x and the OperatorHub

    OpenShift 4.x provides the OperatorHub where you can install the Redis Enterprise Operator from the administrator user interface.

    Getting Started for 3.x and CLI tools

    These are the steps required to set up a Redis Enterprise Software Cluster with OpenShift. Prerequisites: An OpenShift cluster installed (3.x or 4.x) with at least three nodes (each meeting the minimum requirements for a development installation The kubectl package installed at version 1.9 or higher The OpenShift cli installed Step 1: Login Log in to your OpenShift account as a super admin so that you have access to all the default projects.

    Getting Started with Active-Active (CRDB) on OpenShift with Route-Based Ingress

    In this guide, we’ll set up a CRDB (conflict-free replicated database) deployment with Active-Active replication spanning across two Redis Enterprise clusters over OpenShift, using Redis Enterprise Operator and OpenShift Route. Overview A CRDB deployment requires connectivity between different Kubernetes clusters. A router is the most common way to allow such external access. A [router] (https://docs.openshift.com/container-platform/3.5/architecture/core_concepts/routes.html#architecture-core-concepts-routes) is configured to accept requests external to the cluster and proxy them into the cluster based on how the route is configured.