Configuration recommendations on Docs

Manage node resources

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

Node eviction thresholds

Kubernetes uses node-pressure eviction to terminate pods and free up node resources. Redis Enterprise for Kubernetes works best when you use the recommendations below.

Use persistent volumes in Redis Enterprise clusters

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

Storage types

Redis Enterprise for Kubernetes can only use storage classes supported by block storage. Block storage is mounted at the Kubernetes node level and utilizes EXT4 or XFS file systems. It can be sourced from enterprise-grade SANs or cloud environments such as EBS, Azure Managed Disks, or GCP persistent disks.

Size and scale a Redis Enterprise cluster deployment on Kubernetes

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

The following article reviews the mechanism and methods available for sizing and scaling a Redis Enterprise cluster deployment.

For minimum and recommended sizing, always follow the sizing guidelines detailed in the Redis Enterprise hardware requirements.

Sizing and scaling cluster nodes

Setting the number of cluster nodes

Define the number of cluster nodes in redis-enterprise-cluster.yaml file.

Control node selection

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

Kubernetes clusters often include nodes with different CPU and memory profiles. You control where Redis Enterprise cluster (REC) pods run by setting fields in the REC custom resource (CRD).

A Redis Enterprise cluster (REC) runs as a StatefulSet. The Kubernetes scheduler assigns nodes when you create or resize the cluster, or when a pod restarts.

Use these options to control pod placement:

Use node selectors

The nodeSelector field matches the Kubernetes nodeSelector syntax. Label the nodes you want to target. For example, if nodes 'n1' and 'n2' are labeled with memory=high:

Manage pod stability

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

Kubernetes clusters manage the allocation of system resources and can evict pods to release system resources. Here are some ways that you can configure the Redis Enterprise node pods to maintain pod stability:

Guaranteed quality of service

A running pod has a quality of service measure assigned to it that is one of three quality of service classes: Guaranteed, Burstable, and Best Effort. You can assure the Guaranteed class is assigned to the Redis Enterprise node pods by following the right guidelines.