Getting Started with Kubernetes and OpenShift
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.
A quick introduction to the steps necessary to get a Redis Enterprise cluster installed in your OpenShift Kubernetes cluster
OpenShift 4.x provides the OperatorHub where you can install the Redis Enterprise Operator from the administrator user interface. Alternatively, can install the operator and cluster with the CLI.
The operator and cluster can be installed via CLI tools OpenShift 3.x or 4.x.
In this guide, we’ll set up an Active-Active database (formerly known as CRDB) deployment with Active-Active replication spanning across two Redis Enterprise clusters over OpenShift, using Redis Enterprise Operator and OpenShift Route. Overview An Active-Active 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.