Redis Enterprise clusters (REC) on Docs

Connect to the admin console

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

The username and password for the Redis Enterprise Software admin console are stored in a Kubernetes secret. After retrieving your credentials, you can use port forwarding to connect to the admin console.

Note:

There are several methods for accessing the admin console. Port forwarding is the simplest, but not the most efficient method for long-term use. You could also use a load balancer service or Ingress.

Switch to the namespace with your Redis Enterprise cluster (REC).

Manage databases in multiple namespaces

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

Multiple Redis Enterprise database resources (REDBs) can be associated with a single Redis Enterprise cluster resource (REC) even if they reside in different namespaces.

To learn more about designing a multi-namespace Redis Enterprise cluster, see flexible deployment options.

Note:

Multi-namespace installations now support Active-Active databases (REAADB) with certain configuration requirements. For details, see Multi-namespace Active-Active databases.

Prerequisites

Before configuring a multi-namespace deployment, you must have a running Redis Enterprise cluster (REC). See more information in the deployment section.

Recover a Redis Enterprise cluster on Kubernetes

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

When a Redis Enterprise cluster loses contact with more than half of its nodes either because of failed nodes or network split, the cluster stops responding to client connections. When this happens, you must recover the cluster to restore the connections.

You can also perform cluster recovery to reset cluster nodes, to troubleshoot issues, or in a case of active/passive failover.

The Redis Enterprise for Kubernetes automates these recovery steps:

Delete custom resources

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

Multi-namespace management

Before you can delete a namespace, you must remove the Redis custom resources (REDB, REC, and operator) residing within a namespace before you can delete that namespace. Deleting namespace containing an REDB may cause errors or data loss.

Expand PersistentVolumeClaim (PVC)

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

This article outlines steps to increase the size of the persistent volume claim for your Redis Enterprise cluster (REC).

Note:

This feature is only supported in versions 7.4.2-12 and above.

PersistentVolumeClaims (PVC) are created by the Redis Enterprise operator and used by the RedisEnterpriseCluster (REC). PVCs are created with a specific size and can be expanded with the following steps, if the underlying storage class supports it.

Connect the Prometheus operator to Redis Enterprise for Kubernetes

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

To collect metrics data from your databases and Redis Enterprise cluster (REC), you can connect your Prometheus server to an endpoint exposed on your REC. Redis Enterprise for Kubernetes creates a dedicated service to expose the prometheus port (8070) for data collection. A custom resource called ServiceMonitor allows the Prometheus operator to connect to this port and collect data from Redis Enterprise.

Prerequisites

Before connecting Redis Enterprise to Prometheus on your Kubernetes cluster, make sure you've done the following: