Redis Enterprise for Kubernetes 7.4.2-12 (May 2024) release notes

Summary: This is a feature release with a new version of Redis Enterprise Software support for persistent volume expansion.

Highlights

This release has many enhancements, most notably support for persistent volume expansion in the REC. Also, some essential changes in module handling support newer capabilities prompted by changes in the underlying Redis Enterprise around versioning.

New in this release

Enhancements

- Support for persistent volume expansion in the REC (RED-84018)
- Ability to specify Redis version in REDB spec (RED-103945)
- Updated [supported distributions]() (RED-119711)
- Ability to enable modules via REDB without specifying a module version (RED-116082)
- Dual Stack configuration support (RED-121897)

Resolved issues

- Fixed case of client certificates being updated in a loop (RED-121633)
- Fixed issues disabling replication on REDB (RED-122721)

API changes

| **CRD** | **Field** | **Change** | **Description** |
|---|---|---|---|
| REC | spec.persistentSpec.enablePersistentVolumeResize | ADD | Set to "true" to allow changes in volumeSize after REC creation (for sizing up only) |
| REC | status.persistenceStatus | ADD | Indicates the status of persistent volume expansion |
| REC | spec.redisEnterpriseIPFamily | ADD | Configure which IP family to use when Kubernetes cluster has Dual Stack networking enabled  |
| REDB | spec.moduleList[x].version | CHANGE | Field is no longer mandatory |
| REDB | spec.upgradeSpec | ADD | New field allows configuration of module upgrade settings |
| REDB | spec.redisVersion | CHANGE | Now allows setting version numbers (Major.Minor) |

Version changes

For a list of fixes related to CVEs, see the [Redis Enterprise 7.4.2-129 release notes]().

Breaking changes

The following changes included in this release affect the upgrade process. Please read carefully before upgrading.

#### ValidatingWebhookConfiguration

Versions 6.4.2-4 and later include a new `ValidatingWebhookConfiguration` resource to replace the `redb-admission` webhook resource. To use releases 6.4.2-4 or later, delete the old webhook resource and apply the new file. See [upgrade Redis cluster]() for instructions.

#### OpenShift SCC

Versions 6.4.2-6 and later include a new SCC (`redis-enterprise-scc-v2`) that you need to bind to your service account before upgrading. OpenShift clusters running version 6.2.12 or earlier upgrading to version 6.2.18 or later might get stuck if you skip this step. See [upgrade a Redis Enterprise cluster (REC)]() for instructions.

#### Upcoming Changes

- Future Redis Enterprise images will be UBI9-based only, without support for Ubuntu-based images.

Supported distributions

The following table shows supported distributions at the time of this release. You can also find this list in [Supported Kubernetes distributions]().

✅ Supported – This distribution is supported for this version of Redis Enterprise Software for Kubernetes.

:warning: Deprecated – This distribution is still supported for this version of Redis Enterprise Software for Kubernetes, but support will be removed in a future release.

❌ End of life – Support for this distribution ended.

Any distribution not listed below is not supported for production workloads.

| **Kubernetes version** | **1.24** | **1.25** | **1.26** | **1.27** | **1.28** | **1.29** |
|---|---|---|---|---|---|---|
| **Community Kubernetes** |  |  | :warning: | ✅ | ✅ | ✅ |
| **Amazon EKS** |  | :warning: | ✅ | ✅ | ✅ |  |
| **Azure AKS** |  |  | :warning: | ✅ | ✅ | ✅ |
| **Google GKE** |  | :warning: | ✅ | ✅ | ✅ | ✅ |
| **Rancher RKE2** | ❌ | ✅ | ✅ | ✅ |  |  |
| **VMware TKG 2.2** | :warning: | :warning: |  |  |  |  |
| **VMware TKG 2.3** | ✅ | ✅ | ✅ |  |  |  |
| **VMware TKG 2.4** |  | ✅ | ✅ | ✅ |  |  |
| **OpenShift version** | **4.11** | **4.12** | **4.13** | **4.14** | **4.15** |  |
|  | :warning: | ✅ | ✅ | ✅ | ✅ |  |
| **VMware TKGI version** | **1.15** | **1.16** | **1.17** | **1.18** |  |  |
|  | ❌ | ✅ | ✅ | ✅ |  |  |

Downloads

- **Redis Enterprise**: `redislabs/redis:7.4.2-129`
- **Operator**: `redislabs/operator:7.4.2-12`
- **Services Rigger**: `redislabs/k8s-controller:7.4.2-12`

OpenShift images

- **Redis Enterprise**: `registry.connect.redhat.com/redislabs/redis-enterprise:7.4.2-129.rhel8-openshift`
- **Operator**: `registry.connect.redhat.com/redislabs/redis-enterprise-operator:7.4.2-12`
- **Services Rigger**: `registry.connect.redhat.com/redislabs/services-manager:7.4.2-12`

OLM bundle

**Redis Enterprise operator bundle** : `v7.4.2-12.0`

Known limitations

New limitations

- **Missing endpoint for admission endpoint (rare) (RED-119469)** Restart the operator pod.

- **PVC expansion is not supported when using Redis on Flash (Auto Tiering) (RED-165770)** Do not enable `enablePersistentVolumeResize` if your REC uses `redisOnFlashSpec` as this will result in conflicts.

Existing limitations

- **The REDB "redisVersion" field can’t be used for memcached databases(RED-119152)**

- **When modifying the database suffix for an Active-Active database, while the service-rigger is in a terminating state, the services-rigger will delete and create the ingress or route resources in a loop (RED-107687)** Wait until the services rigger pod has finished to terminate it.

- **REAADB changes might fail with "gateway timeout" errors, mostly on OpenShift (RED-103048)** Retry the operation.

- **Creating two databases with the same name directly on Redis Enterprise software will cause the service to be deleted and the database will not be available (RED-99997)** Avoid duplicating database names. Database creation via K8s has validation in place to prevent this.

- **Installing the operator bundle produces warning: `Warning: would violate PodSecurity "restricted: v1.24"` (RED-97381)** Ignore the warning. This issue is documented as benign on official Red Hat documentation.

- **RERC resources must have a unique name (RED-96302)** The string "rec-name"/"rec-namespace" must be different from all other participating clusters in the Active-Active database.

- **Admission is not blocking REAADB with `shardCount` which exceeds license quota (RED-96301)** Fix the problems with the REAADB and reapply.

- **Active-Active controller only supports global database options. Configuration specific to location is not supported (RED-86490)**

- **Active-Active setup removal might keep services or routes undeleted (RED-77752)** Delete services or routes manually if you encounter this problem.

- **`autoUpgrade` set to `true` can cause unexpected bdb upgrades when `redisUpgradePolicy` is set to `true` (RED-72351)** Contact support if your deployment is impacted.

- **Following the previous quick start guide version causes issues with creating an REDB due to unrecognized memory field name (RED-69515)** The workaround is to use the newer (current) revision of Deploy Redis Enterprise Software for Kubernetes.

- **PVC size issues when using decimal value in spec (RED-62132)** Make sure you use integer values for the PVC size.

- **REC might report error states on initial startup (RED-61707)** There is no workaround at this time except to ignore the errors.

- **Hashicorp Vault integration - no support for Gesher (RED-55080)** There is no workaround for this issue. Gesher support has been deprecated.

- **REC clusters fail to start on Kubernetes clusters with unsynchronized clocks (RED-47254)** When REC clusters are deployed on Kubernetes clusters without synchronized clocks, the REC cluster does not start correctly. The fix is to use NTP to synchronize the underlying K8s nodes.

- **Deleting an OpenShift project with an REC deployed may hang (RED-47192)** When an REC cluster is deployed in a project (namespace) and has REDB resources, the REDB resources must be deleted first before the REC can be deleted. Therefore, until the REDB resources are deleted, the project deletion will hang. The fix is to delete the REDB resources first and the REC second. Then, you can delete the project.

- **Clusters must be named 'rec' in OLM-based deployments (RED-39825)** In OLM-deployed operators, the deployment of the cluster will fail if the name is not "rec". When the operator is deployed via the OLM, the security context constraints (scc) are bound to a specific service account name (namely, "rec"). The workaround is to name the cluster "rec".

- **Readiness probe incorrect on failures (RED-39300)** STS Readiness probe does not mark a node as "not ready" when running `rladmin status` on node failure.

- **Internal DNS and Kubernetes DNS may have conflicts (RED-37462)** DNS conflicts are possible between the cluster `mdns_server` and the K8s DNS. This only impacts DNS resolution from within cluster nodes for Kubernetes DNS names.

- **K8s-based 5.4.10 clusters seem to negatively affect existing 5.4.6 clusters (RED-37233)** Upgrade clusters to latest version.

- **Node CPU usage is reported instead of pod CPU usage (RED-36884)** In Kubernetes, the reported node CPU usage is the usage of the Kubernetes worker node hosting the REC pod.

- **An unreachable cluster has status running (RED-32805)** When a cluster is in an unreachable state, the state remains `running` instead of triggering an error.

- **Long cluster names cause routes to be rejected  (RED-25871)** A cluster name longer than 20 characters will result in a rejected route configuration because the host part of the domain name exceeds 63 characters. The workaround is to limit the cluster name to 20 characters or fewer.

- **Cluster CR (REC) errors are not reported after invalid updates (RED-25542)** A cluster CR specification error is not reported if two or more invalid CR resources are updated in sequence.


Redis Enterprise for Kubernetes 7.4.2-2 (Feb 2024) release notes

Summary: The primary purpose of this release is to support Redis Enterprise 7.4.2

Highlights

The primary purpose of this release is to support [Redis Enterprise 7.4.2](), which is a major update to Redis Enterprise Software. As such, we have limited the scope of changes to focus on supporting RS 7.4 changes, in addition to implementing a few enhancements and major fixes.

New in this release

Enhancements

- Added RESP3 support in K8s APIs (RED-94601)
- Added to [supported distributions](#supported-distributions)
- Added support for Redis Enterprise Software 7.4.2
- Enhanced resilience of operators to misconfigured REDB namespaces (RED-113908)
- Both the operator and services rigger are now based on UBI9 (RED-116083)

Resolved issues

- Fixed the operator to prevent reconciliation of non-REDB custom resources in observed namespaces. This eliminates the need for unnecessary permission rules. (RED-87790)
- Fixed excessive updates to ingresses and services. (RED-109289)
- Fixed update issues in rigger after the upgrade in multi-namespace environments. (RED-111732)
- Fixed Active-Active sharding configuration by adding a new field. (RED-112909)
- Fixed operator CVE. (RED-115157)
- Fixed a race condition that could have rarely caused the cluster upgrade to break. (RED-118940)

API changes

| **CRD** | **Field** | **Change** | **Description** |
|---|---|---|---|
| REC | resp3Default | Add | Boolean controlling whether Resp3 should be enabled by default |
| REDB | resp3 | Add | Controls resp3 for specific REDBs |

Version changes

For a list of fixes related to CVEs, see the [Redis Enterprise 7.4.2-54 release notes]().

Breaking changes

The following changes included in this release affect the upgrade process. Please read carefully before upgrading.

#### Upgrade operating system

If your databases use modules, you need to update all nodes in the cluster to Redis Enterprise 7.2.4 or later before upgrading your operating system. See [Upgrade a cluster's operating system]()in the Redis Enterprise Software documentation for more details.

#### terminationGracePeriodSeconds

The configurable `terminationGracePeriodSeconds` REC field was added in version 7.2.4-12 to replace the hard-coded timeout of 15 minutes for a node to be stopped or drained (RED-111471).

#### ValidatingWebhookConfiguration

Versions 6.4.2-4 and later include a new `ValidatingWebhookConfiguration` resource to replace the `redb-admission` webhook resource. To use releases 6.4.2-4 or later, delete the old webhook resource and apply the new file. See [upgrade Redis cluster]() for instructions.

#### OpenShift SCC

Versions 6.4.2-6 and later include a new SCC (`redis-enterprise-scc-v2`) that you need to bind to your service account before upgrading. OpenShift clusters running version 6.2.12 or earlier upgrading to version 6.2.18 or later might get stuck if you skip this step. See [upgrade a Redis Enterprise cluster (REC)]() for instructions.

Deprecations

- Redis Software for Kubernetes no longer supports the RHEL7 operating system. Migrate to RHEL8 to use this version.

Supported distributions

See the [7.4.2 releases]() page for the list of supported distributions.

Downloads

- **Redis Enterprise**: `redislabs/redis:7.4.2-54`
- **Operator**: `redislabs/operator:7.4.2-2`
- **Services Rigger**: `redislabs/k8s-controller:7.4.2-2`

#### OpenShift images

- **Redis Enterprise**: `registry.connect.redhat.com/redislabs/redis-enterprise:7.4.2-54.rhel8-openshift`
- **Operator**: `registry.connect.redhat.com/redislabs/redis-enterprise-operator:7.4.2-2`
- **Services Rigger**: `registry.connect.redhat.com/redislabs/services-manager:7.4.2-2`

#### OLM bundle

**Redis Enterprise operator bundle** : `v7.4.2-2`

Known limitations

See the [7.4.2 releases]() page for the list of known limitations.


Redis Enterprise for Kubernetes 7.4.2 release notes

Summary: Releases with support for Redis Enterprise Software 7.4.2.

Summary: This is a maintenance release supporting Redis Enterprise Software 7.4.2.

Redis Enterprise for Kubernetes 7.4.2-2 (March 2024) release notes

Detailed release notes

Version changes

For a list of fixes related to CVEs, see the [Redis Enterprise 7.4.6-22 release notes]().

Breaking changes

Deprecations

Supported distributions

The following table shows supported distributions at the time of this release. You can also find this list in [Supported Kubernetes distributions]().

✅ Supported – This distribution is supported for this version of Redis Enterprise Software for Kubernetes.

:warning: Deprecated – This distribution is still supported for this version of Redis Enterprise Software for Kubernetes, but support will be removed in a future release.

❌ End of life – Support for this distribution ended.

Any distribution not listed below is not supported for production workloads.

| **Kubernetes version** | **1.24** | **1.25** | **1.26** | **1.27** | **1.28** | **1.29** |
|---|---|---|---|---|---|---|
| **Community Kubernetes** | ❌ | ❌ | :warning: | ✅ | ✅ | ✅ |
| **Amazon EKS** | :warning: | :warning: | ✅ | ✅ | ✅ |  |
| **Azure AKS** | ❌ | ❌ | :warning: | ✅ | ✅ |  |
| **Google GKE** | ❌ | :warning: | ✅ | ✅ | ✅ |  |
| **Rancher RKE2** | :warning: | ✅ | ✅ | ✅ |  |  |
| **VMware TKG 2.2** | :warning: | :warning: |  |  |  |  |
| **VMware TKG 2.3** | ✅ | ✅ | ✅ |  |  |  |
| **VMware TKG 2.4** |  | ✅ | ✅ | ✅ |  |  |
| **OpenShift version** | **4.11** | **4.12** | **4.13** | **4.14** |  |  |
|  | :warning: | :warning: | ✅ | ✅ |  |  |
| **VMware TKGI version** | **1.15** | **1.16** | **1.17** | **1.18** |  |  |
|  | ✅ | ✅ | ✅ | ✅ |  |  |

Known limitations

The limitations below are specific to the Redis Enterprise for Kubernetes product. To view limitations for the supported Redis Enterprise Software version, see the [7.4.2 release notes]().

New limitations

- **Missing endpoint for admission endpoint (rare) (RED-119469)** Restart the operator pod.
- **The REDB "redisVersion" field can’t be used for memcached databases(RED-119152)**

Existing limitations

- **When modifying the database suffix for an Active-Active database, while the service-rigger is in a terminating state, the services-rigger will delete and create the ingress or route resources in a loop (RED-107687)** Wait until the services- rigger pod has finished to terminate it.

- **REAADB changes might fail with "gateway timeout" errors, mostly on OpenShift (RED-103048)** Retry the operation.

- **Creating two databases with the same name directly on Redis Enterprise software will cause the service to be deleted and the database will not be available (RED-99997)** Avoid duplicating database names. Database creation via K8s has validation in place to prevent this.

- **Installing the operator bundle produces warning: `Warning: would violate PodSecurity "restricted: v1.24"` (RED-97381)** Ignore the warning. This issue is documented as benign on official Red Hat documentation.

- **RERC resources must have a unique name (RED-96302)** The string "rec-name"/"rec-namespace" must be different from all other participating clusters in the Active-Active database.

- **Admission is not blocking REAADB with `shardCount` which exceeds license quota (RED-96301)** Fix the problems with the REAADB and reapply.

- **Active-Active controller only supports global database options. Configuration specific to location is not supported (RED-86490)**

- **Active-Active setup removal might keep services or routes undeleted (RED-77752)** Delete services or routes manually if you encounter this problem.

- **`autoUpgrade` set to `true` can cause unexpected bdb upgrades when `redisUpgradePolicy` is set to `true` (RED-72351)** Contact support if your deployment is impacted.

- **Following the previous quick start guide version causes issues with creating an REDB due to unrecognized memory field name (RED-69515)** The workaround is to use the newer (current) revision of Deploy Redis Enterprise Software for Kubernetes.

- **PVC size issues when using decimal value in spec (RED-62132)** Make sure you use integer values for the PVC size.

- **REC might report error states on initial startup (RED-61707)** There is no workaround at this time except to ignore the errors.

- **Hashicorp Vault integration - no support for Gesher (RED-55080)** There is no workaround for this issue. Gesher support has been deprecated.

- **REC clusters fail to start on Kubernetes clusters with unsynchronized clocks (RED-47254)** When REC clusters are deployed on Kubernetes clusters without synchronized clocks, the REC cluster does not start correctly. The fix is to use NTP to synchronize the underlying K8s nodes.

- **Deleting an OpenShift project with an REC deployed may hang (RED-47192)** When an REC cluster is deployed in a project (namespace) and has REDB resources, the REDB resources must be deleted first before the REC can be deleted. Therefore, until the REDB resources are deleted, the project deletion will hang. The fix is to delete the REDB resources first and the REC second. Then, you can delete the project.

- **Clusters must be named 'rec' in OLM-based deployments (RED-39825)** In OLM-deployed operators, the deployment of the cluster will fail if the name is not "rec". When the operator is deployed via the OLM, the security context constraints (scc) are bound to a specific service account name (namely, "rec"). The workaround is to name the cluster "rec".

- **Readiness probe incorrect on failures (RED-39300)** STS Readiness probe does not mark a node as "not ready" when running `rladmin status` on node failure.

- **Internal DNS and Kubernetes DNS may have conflicts (RED-37462)** DNS conflicts are possible between the cluster `mdns_server` and the K8s DNS. This only impacts DNS resolution from within cluster nodes for Kubernetes DNS names.

- **K8s-based 5.4.10 clusters seem to negatively affect existing 5.4.6 clusters (RED-37233)** Upgrade clusters to latest version.

- **Node CPU usage is reported instead of pod CPU usage (RED-36884)** In Kubernetes, the reported node CPU usage is the usage of the Kubernetes worker node hosting the REC pod.

- **An unreachable cluster has status running (RED-32805)** When a cluster is in an unreachable state, the state remains `running` instead of triggering an error.

- **Long cluster names cause routes to be rejected  (RED-25871)** A cluster name longer than 20 characters will result in a rejected route configuration because the host part of the domain name exceeds 63 characters. The workaround is to limit the cluster name to 20 characters or fewer.

- **Cluster CR (REC) errors are not reported after invalid updates (RED-25542)** A cluster CR specification error is not reported if two or more invalid CR resources are updated in sequence.


Redis Enterprise for Kubernetes 7.4.6-2 (July 2024) release notes

Summary: This is a feature release with a new version of Redis Enterprise Software 7.4.6.

Highlights

The primary purpose of this release is to support [Redis Enterprise Software version 7.4.6](). It also includes updates to supported platform distributions.

New in this release

Enhancements

- Removal of multiple unneeded permissions from RBAC roles used by the operator (RED-123478 RED-125020)
- Support for non-AWS S3 compatible backup targets in REC (RED-73642)
- Support for Redis Enterprise 7.4.6-22 (RED-13110)

API changes

| **CRD** | **Field** | **Change** | **Description** |
|---|---|---|---|
| REC | backup.s3.caCertificateSecretName | Add | Secret name that holds the S3 CA certificate, which contains the TLS certificate mapped to the key in the secret 'cert' |
| REC | backup.s3.url | Add | Specifies the URL for S3 export and import (used for custom S3 compatible servers) |

Version changes

For a list of fixes related to CVEs, see the [Redis Enterprise 7.2.4-109 release notes]().

Breaking changes

The following changes included in this release affect the upgrade process. Please read carefully before upgrading.

#### ValidatingWebhookConfiguration

Versions 6.4.2-4 and later include a new `ValidatingWebhookConfiguration` resource to replace the `redb-admission` webhook resource. To use releases 6.4.2-4 or later, delete the old webhook resource and apply the new file. See [upgrade Redis cluster]() for instructions.

#### OpenShift SCC

Versions 6.4.2-6 and later include a new SCC (`redis-enterprise-scc-v2`) that you need to bind to your service account before upgrading. OpenShift clusters running version 6.2.12 or earlier upgrading to version 6.2.18 or later might get stuck if you skip this step. See [upgrade a Redis Enterprise cluster (REC)]() for instructions.

#### Upcoming Changes

- Future Redis Enterprise images will be UBI9-based only, without support for Ubuntu-based images.

Supported distributions

The following table shows supported distributions at the time of this release. You can also find this list in [Supported Kubernetes distributions]().

✅ Supported – This distribution is supported for this version of Redis Enterprise Software for Kubernetes.

:warning: Deprecated – This distribution is still supported for this version of Redis Enterprise Software for Kubernetes, but support will be removed in a future release.

❌ End of life – Support for this distribution ended.

Any distribution not listed below is not supported for production workloads.

| **Kubernetes version** | **1.25** | **1.26** | **1.27** | **1.28** | **1.29** | **1.30** |
|---|---|---|---|---|---|---|
| **Community Kubernetes** |  | :warning: | ✅ | ✅ | ✅ | ✅ |
| **Amazon EKS** | ❌ | :warning: | :warning: | ✅ | ✅ |  |
| **Azure AKS** |  | ❌ | :warning: | ✅ | ✅ | ✅ |
| **Google GKE** | ❌ | :warning: | :warning: | ✅ | ✅ | ✅ |
| **Rancher RKE2** | :warning: | ✅ | ✅ | ✅ |  |  |
| **VMware TKG 2.2** | ❌ |  |  |  |  |  |
| **VMware TKG 2.3** | ❌ | ✅ |  |  |  |  |
| **VMware TKG 2.4** | ✅ | ✅ | ✅ |  |  |  |
| **OpenShift version** | **4.12** | **4.13** | **4.14** | **4.15** | **4.16** |  |
|  | ✅ | ✅ | ✅ | ✅ | ✅ |  |
| **VMware TKGI version** | **1.16** | **1.17** | **1.18** | **1.19** |  |  |
|  | :warning: | ✅ | ✅ | ✅ |  |  |

Downloads

- **Redis Enterprise**: `redislabs/redis:7.4.6-22`
- **Operator**: `redislabs/operator:7.4.6-2`
- **Services Rigger**: `redislabs/k8s-controller:7.4.6-2`

OpenShift images

- **Redis Enterprise**: `registry.connect.redhat.com/redislabs/redis-enterprise:7.4.6-22.rhel8-openshift`
- **Operator**: `registry.connect.redhat.com/redislabs/redis-enterprise-operator:7.4.6-2`
- **Services Rigger**: `registry.connect.redhat.com/redislabs/services-manager:7.4.6-2`

OLM bundle

**Redis Enterprise operator bundle** : `v7.4.6-2.0`

Known limitations

- **Missing endpoint for admission endpoint (rare) (RED-119469)** Restart the operator pod.

- **The REDB "redisVersion" field can’t be used for memcached databases(RED-119152)**

- **PVC expansion is not supported when using Redis on Flash (Auto Tiering) (RED-165770)** Do not enable `enablePersistentVolumeResize` if your REC uses `redisOnFlashSpec` as this will result in conflicts.

- **When modifying the database suffix for an Active-Active database, while the service-rigger is in a terminating state, the services-rigger will delete and create the ingress or route resources in a loop (RED-107687)** Wait until the services rigger pod has finished to terminate it.

- **REAADB changes might fail with "gateway timeout" errors, mostly on OpenShift (RED-103048)** Retry the operation.

- **Creating two databases with the same name directly on Redis Enterprise software will cause the service to be deleted and the database will not be available (RED-99997)** Avoid duplicating database names. Database creation via K8s has validation in place to prevent this.

- **Installing the operator bundle produces warning: `Warning: would violate PodSecurity "restricted: v1.24"` (RED-97381)** Ignore the warning. This issue is documented as benign on official Red Hat documentation.

- **RERC resources must have a unique name (RED-96302)** The string "rec-name"/"rec-namespace" must be different from all other participating clusters in the Active-Active database.

- **Admission is not blocking REAADB with `shardCount` which exceeds license quota (RED-96301)** Fix the problems with the REAADB and reapply.

- **Active-Active controller only supports global database options. Configuration specific to location is not supported (RED-86490)**

- **Active-Active setup removal might keep services or routes undeleted (RED-77752)** Delete services or routes manually if you encounter this problem.

- **`autoUpgrade` set to `true` can cause unexpected bdb upgrades when `redisUpgradePolicy` is set to `true` (RED-72351)** Contact support if your deployment is impacted.

- **Following the previous quick start guide version causes issues with creating an REDB due to unrecognized memory field name (RED-69515)** The workaround is to use the newer (current) revision of Deploy Redis Enterprise Software for Kubernetes.

- **PVC size issues when using decimal value in spec (RED-62132)** Make sure you use integer values for the PVC size.

- **REC might report error states on initial startup (RED-61707)** There is no workaround at this time except to ignore the errors.

- **Hashicorp Vault integration - no support for Gesher (RED-55080)** There is no workaround for this issue. Gesher support has been deprecated.

- **REC clusters fail to start on Kubernetes clusters with unsynchronized clocks (RED-47254)** When REC clusters are deployed on Kubernetes clusters without synchronized clocks, the REC cluster does not start correctly. The fix is to use NTP to synchronize the underlying K8s nodes.

- **Deleting an OpenShift project with an REC deployed may hang (RED-47192)** When an REC cluster is deployed in a project (namespace) and has REDB resources, the REDB resources must be deleted first before the REC can be deleted. Therefore, until the REDB resources are deleted, the project deletion will hang. The fix is to delete the REDB resources first and the REC second. Then, you can delete the project.

- **Clusters must be named 'rec' in OLM-based deployments (RED-39825)** In OLM-deployed operators, the deployment of the cluster will fail if the name is not "rec". When the operator is deployed via the OLM, the security context constraints (scc) are bound to a specific service account name (namely, "rec"). The workaround is to name the cluster "rec".

- **Readiness probe incorrect on failures (RED-39300)** STS Readiness probe does not mark a node as "not ready" when running `rladmin status` on node failure.

- **Internal DNS and Kubernetes DNS may have conflicts (RED-37462)** DNS conflicts are possible between the cluster `mdns_server` and the K8s DNS. This only impacts DNS resolution from within cluster nodes for Kubernetes DNS names.

- **K8s-based 5.4.10 clusters seem to negatively affect existing 5.4.6 clusters (RED-37233)** Upgrade clusters to latest version.

- **Node CPU usage is reported instead of pod CPU usage (RED-36884)** In Kubernetes, the reported node CPU usage is the usage of the Kubernetes worker node hosting the REC pod.

- **An unreachable cluster has status running (RED-32805)** When a cluster is in an unreachable state, the state remains `running` instead of triggering an error.

- **Long cluster names cause routes to be rejected  (RED-25871)** A cluster name longer than 20 characters will result in a rejected route configuration because the host part of the domain name exceeds 63 characters. The workaround is to limit the cluster name to 20 characters or fewer.

- **Cluster CR (REC) errors are not reported after invalid updates (RED-25542)** A cluster CR specification error is not reported if two or more invalid CR resources are updated in sequence.


Redis Enterprise for Kubernetes 7.4.6-2 (October 2024) release notes

Summary: This is a maintenance release with a new version of Redis Enterprise Software 7.4.6.

Highlights

This is a maintenance release to support [Redis Enterprise Software version 7.4.6-77](). For version changes, supported distributions, and known limitations, see the [release notes for 7-4-6-2 (July 2024)]().

Downloads

- **Redis Enterprise**: `redislabs/redis:7.4.6-77`
- **Operator**: `redislabs/operator:7.4.6-2`
- **Services Rigger**: `redislabs/k8s-controller:7.4.6-2`

OpenShift images

- **Redis Enterprise**: `registry.connect.redhat.com/redislabs/redis-enterprise:7.4.6-77.rhel8-openshift`
- **Operator**: `registry.connect.redhat.com/redislabs/redis-enterprise-operator:7.4.6-2`
- **Services Rigger**: `registry.connect.redhat.com/redislabs/services-manager:7.4.6-2`

OLM bundle

**Redis Enterprise operator bundle** : `v7.4.6-2.3`


Highlights

This is a maintenance release to support [Redis Enterprise Software version 7.4.6-102](). For version changes, supported distributions, and known limitations, see the [release notes for 7-4-6-2 (July 2024)]().

Downloads

- **Redis Enterprise**: `redislabs/redis:7.4.6-102`
- **Operator**: `redislabs/operator:7.4.6-2`
- **Services Rigger**: `redislabs/k8s-controller:7.4.6-2`

OpenShift images

- **Redis Enterprise**: `registry.connect.redhat.com/redislabs/redis-enterprise:7.4.6-102.rhel8-openshift`
- **Operator**: `registry.connect.redhat.com/redislabs/redis-enterprise-operator:7.4.6-2`
- **Services Rigger**: `registry.connect.redhat.com/redislabs/services-manager:7.4.6-2`

OLM bundle

**Redis Enterprise operator bundle** : `v7.4.6-2.4`

The OLM version v7.4.6-2.4 replaces the earlier v7.4.6-2.3 release for the same Redis software version, providing only upgrade path fixes.


Redis Enterprise for Kubernetes 7.4.6-6 (Dec 2024) release notes

Summary: This is a maintenance release to support Redis Enterprise Software version 7.4.6-102 and contains a suggested fix needed to upgrade to newer versions.

Highlights

This is a maintenance release to support [Redis Enterprise Software version 7.4.6-102](). This version also contains a suggested fix needed to upgrade to newer versions. For version changes, supported distributions, and known limitations, see the [release notes for 7-4-6-2 (July 2024)]().

New in this release

Resolved issues

- Fixed service rigger crashing after REC upgrade (RED-144785)

Downloads

- **Redis Enterprise**: `redislabs/redis:7.4.6-102`
- **Operator**: `redislabs/operator:7.4.6-6`
- **Services Rigger**: `redislabs/k8s-controller:7.4.6-6`

OpenShift images

- **Redis Enterprise**: `registry.connect.redhat.com/redislabs/redis-enterprise:7.4.6-102.rhel8-openshift`
- **Operator**: `registry.connect.redhat.com/redislabs/redis-enterprise-operator:7.4.6-6`
- **Services Rigger**: `registry.connect.redhat.com/redislabs/services-manager:7.4.6-6`
- **OLM operator bundle** : `v7.4.6-6.1`


Redis Enterprise for Kubernetes 7.4.6-6 (June 2025) release notes

Summary: This is a maintenance release to support Redis Enterprise Software version 7.4.6-268.

Highlights

This is a maintenance release to support [Redis Enterprise Software version 7.4.6-268](). For version changes, supported distributions, and known limitations, see the [release notes for 7.4.6]().

Downloads

- **Redis Enterprise**: `redislabs/redis:7.4.6-268`
- **Operator**: `redislabs/operator:7.4.6-6`
- **Services Rigger**: `redislabs/k8s-controller:7.4.6-6`

OpenShift images

- **Redis Enterprise**: `registry.connect.redhat.com/redislabs/redis-enterprise:7.4.6-268.rhel8-openshift`
- **Operator**: `registry.connect.redhat.com/redislabs/redis-enterprise-operator:7.4.6-6`
- **Services Rigger**: `registry.connect.redhat.com/redislabs/services-manager:7.4.6-6`
- **OLM operator bundle**: `v7.4.6-6.4`


Redis Enterprise for Kubernetes 7.4.6-6 (March 2025) release notes

Summary: This is a maintenance release to support Redis Enterprise Software version 7.4.6-233 (7.4.6-232 for OpenShift).

Highlights

This is a maintenance release to support [Redis Enterprise Software version 7.4.6-232](). For version changes, supported distributions, and known limitations, see the [release notes for 7.4.6]().

If you are not using OpenShift, you must use the `7.4.6-233` Redis Enterprise image listed below. The `7.4.6-232` image only supports OpenShift, and may cause the upgrade to fail if used with other distributions.

To upgrade successfully, use the correct Redis Enterprise image for your K8s distribution.

- OpenShift: `registry.connect.redhat.com/redislabs/redis-enterprise:7.4.6-232.rhel8-openshift`
- Non-OpenShift distributions: `redislabs/redis:7.4.6-233`

Downloads

- **Redis Enterprise**: `redislabs/redis:7.4.6-233`
- **Operator**: `redislabs/operator:7.4.6-6`
- **Services Rigger**: `redislabs/k8s-controller:7.4.6-6`

OpenShift images

- **Redis Enterprise**: `registry.connect.redhat.com/redislabs/redis-enterprise:7.4.6-232.rhel8-openshift`
- **Operator**: `registry.connect.redhat.com/redislabs/redis-enterprise-operator:7.4.6-6`
- **Services Rigger**: `registry.connect.redhat.com/redislabs/services-manager:7.4.6-6`
- **OLM operator bundle**: `v7.4.6-6.3`


Redis Enterprise for Kubernetes 7.4.6-7 (December 2025) release notes

Highlights

This is a maintenance release to support Redis Enterprise Software version 7.4.6-275. For version changes, supported distributions, and known limitations, see the [release notes for 7.4.6]().

Downloads

- **Redis Enterprise**: `redislabs/redis:7.4.6-275`
- **Operator**: `redislabs/operator:7.4.6-7`
- **Services Rigger**: `redislabs/k8s-controller:7.4.6-7`

OpenShift images

- **Redis Enterprise**: `registry.connect.redhat.com/redislabs/redis-enterprise:7.4.6-275.rhel8-openshift`
- **Operator**: `registry.connect.redhat.com/redislabs/redis-enterprise-operator:7.4.6-7`
- **Services Rigger**: `registry.connect.redhat.com/redislabs/services-manager:7.4.6-7`
- **OLM operator bundle**: `7.4.6-7.5`


Redis Enterprise for Kubernetes 7.4.6-7 (September 2025) release notes

Summary: This is a maintenance release to support Redis Enterprise Software version 7.4.6-272.

Highlights

This is a maintenance release to support [Redis Enterprise Software version 7.4.6-272](). For version changes, supported distributions, and known limitations, see the [release notes for 7.4.6]().

Downloads

- **Redis Enterprise**: `redislabs/redis:7.4.6-272`
- **Operator**: `redislabs/operator:7.4.6-7`
- **Services Rigger**: `redislabs/k8s-controller:7.4.6-7`

OpenShift images

- **Redis Enterprise**: `registry.connect.redhat.com/redislabs/redis-enterprise:7.4.6-272.rhel8-openshift`
- **Operator**: `registry.connect.redhat.com/redislabs/redis-enterprise-operator:7.4.6-7`
- **Services Rigger**: `registry.connect.redhat.com/redislabs/services-manager:7.4.6-7`
- **OLM operator bundle**: `v7.4.6-7.2`


Redis Enterprise for Kubernetes 7.4.6-9 (February 2026) release notes

Summary: This is a maintenance release to support Redis Enterprise Software version 7.4.6-279.

Highlights

This is a maintenance release to support [Redis Enterprise Software version 7.4.6-279](). For version changes, supported distributions, and known limitations, see the [release notes for 7.4.6]().

Downloads

- **Redis Enterprise**: `redislabs/redis:7.4.6-279`
- **Operator**: `redislabs/operator:7.4.6-9`
- **Services Rigger**: `redislabs/k8s-controller:7.4.6-9`

OpenShift images

- **Redis Enterprise**: `registry.connect.redhat.com/redislabs/redis-enterprise:7.4.6-279.rhel8-openshift`
- **Operator**: `registry.connect.redhat.com/redislabs/redis-enterprise-operator:7.4.6-9`
- **Services Rigger**: `registry.connect.redhat.com/redislabs/services-manager:7.4.6-9`

OLM bundle

**Redis Enterprise operator bundle**: `v7.4.6-9.0`


Redis Enterprise for Kubernetes 7.4.6 release notes

Summary: Releases with support for Redis Enterprise Software 7.4.6.

Detailed release notes

Breaking changes

The following changes included in this release affect the upgrade process. Please read carefully before upgrading.

ValidatingWebhookConfiguration

Versions 6.4.2-4 and later include a new `ValidatingWebhookConfiguration` resource to replace the `redb-admission` webhook resource. To use releases 6.4.2-4 or later, delete the old webhook resource and apply the new file. See [upgrade Redis cluster]() for instructions.

OpenShift SCC

Versions 6.4.2-6 and later include a new SCC (`redis-enterprise-scc-v2`) that you need to bind to your service account before upgrading. If you skip this step, OpenShift clusters running version 6.2.12 or earlier might get stuck when upgrading to version 6.2.18 or later. See [upgrade a Redis Enterprise cluster (REC)]() for instructions.

Upcoming Changes

- Future Redis Enterprise images will be UBI9-based only, without support for Ubuntu-based images.

Security

For a list of fixes related to CVEs, see the [Redis Enterprise 7.2.4-109 release notes]().

Supported distributions

The following table shows supported distributions at the time of this release. You can also find this list in [Supported Kubernetes distributions]().

✅ Supported – This distribution is supported for this version of Redis Enterprise Software for Kubernetes.

:warning: Deprecated – This distribution is still supported for this version of Redis Enterprise Software for Kubernetes, but support will be removed in a future release.

❌ End of life – Support for this distribution ended.

Any distribution not listed below is not supported for production workloads.

| **Kubernetes version** | **1.25** | **1.26** | **1.27** | **1.28** | **1.29** | **1.30** |
|---|---|---|---|---|---|---|
| **Community Kubernetes** |  | :warning: | ✅ | ✅ | ✅ | ✅ |
| **Amazon EKS** | ❌ | :warning: | :warning: | ✅ | ✅ |  |
| **Azure AKS** |  | ❌ | :warning: | ✅ | ✅ | ✅ |
| **Google GKE** | ❌ | :warning: | :warning: | ✅ | ✅ | ✅ |
| **Rancher RKE2** | :warning: | ✅ | ✅ | ✅ |  |  |
| **VMware TKG 2.2** | ❌ |  |  |  |  |  |
| **VMware TKG 2.3** | ❌ | ✅ |  |  |  |  |
| **VMware TKG 2.4** | ✅ | ✅ | ✅ |  |  |  |
| **OpenShift version** | **4.12** | **4.13** | **4.14** | **4.15** | **4.16** |  |
|  | ✅ | ✅ | ✅ | ✅ | ✅ |  |
| **VMware TKGI version** | **1.16** | **1.17** | **1.18** | **1.19** |  |  |
|  | :warning: | ✅ | ✅ | ✅ |  |  |

Known limitations

- **Missing endpoint for admission endpoint (rare) (RED-119469)** Restart the operator pod.

- **The REDB "redisVersion" field can’t be used for memcached databases(RED-119152)**

- **When modifying the database suffix for an Active-Active database, while the service-rigger is in a terminating state, the services-rigger will delete and create the ingress or route resources in a loop (RED-107687)** Wait until the services rigger pod has finished to terminate it.

- **REAADB changes might fail with "gateway timeout" errors, mostly on OpenShift (RED-103048)** Retry the operation.

- **Creating two databases with the same name directly on Redis Enterprise software will cause the service to be deleted and the database will not be available (RED-99997)** Avoid duplicating database names. Database creation via K8s has validation in place to prevent this.

- **Installing the operator bundle produces warning: `Warning: would violate PodSecurity "restricted: v1.24"` (RED-97381)** Ignore the warning. This issue is documented as benign on official Red Hat documentation.

- **RERC resources must have a unique name (RED-96302)** The string "rec-name"/"rec-namespace" must be different from all other participating clusters in the Active-Active database.

- **Admission is not blocking REAADB with `shardCount` which exceeds license quota (RED-96301)** Fix the problems with the REAADB and reapply.

- **Active-Active controller only supports global database options. Configuration specific to location is not supported (RED-86490)**

- **Active-Active setup removal might keep services or routes undeleted (RED-77752)** Delete services or routes manually if you encounter this problem.

- **`autoUpgrade` set to `true` can cause unexpected bdb upgrades when `redisUpgradePolicy` is set to `true` (RED-72351)** Contact support if your deployment is impacted.

- **Following the previous quick start guide version causes issues with creating an REDB due to unrecognized memory field name (RED-69515)** The workaround is to use the newer (current) revision of Deploy Redis Enterprise Software for Kubernetes.

- **PVC size issues when using decimal value in spec (RED-62132)** Make sure you use integer values for the PVC size.

- **REC might report error states on initial startup (RED-61707)** There is no workaround at this time except to ignore the errors.

- **Hashicorp Vault integration - no support for Gesher (RED-55080)** There is no workaround for this issue. Gesher support has been deprecated.

- **REC clusters fail to start on Kubernetes clusters with unsynchronized clocks (RED-47254)** When REC clusters are deployed on Kubernetes clusters without synchronized clocks, the REC cluster does not start correctly. The fix is to use NTP to synchronize the underlying K8s nodes.

- **Deleting an OpenShift project with an REC deployed may hang (RED-47192)** When an REC cluster is deployed in a project (namespace) and has REDB resources, the REDB resources must be deleted first before the REC can be deleted. Therefore, until the REDB resources are deleted, the project deletion will hang. The fix is to delete the REDB resources first and the REC second. Then, you can delete the project.

- **Clusters must be named 'rec' in OLM-based deployments (RED-39825)** In OLM-deployed operators, the deployment of the cluster will fail if the name is not "rec". When the operator is deployed via the OLM, the security context constraints (scc) are bound to a specific service account name (namely, "rec"). The workaround is to name the cluster "rec".

- **Readiness probe incorrect on failures (RED-39300)** STS Readiness probe does not mark a node as "not ready" when running `rladmin status` on node failure.

- **Internal DNS and Kubernetes DNS may have conflicts (RED-37462)** DNS conflicts are possible between the cluster `mdns_server` and the K8s DNS. This only impacts DNS resolution from within cluster nodes for Kubernetes DNS names.

- **K8s-based 5.4.10 clusters seem to negatively affect existing 5.4.6 clusters (RED-37233)** Upgrade clusters to latest version.

- **Node CPU usage is reported instead of pod CPU usage (RED-36884)** In Kubernetes, the reported node CPU usage is the usage of the Kubernetes worker node hosting the REC pod.

- **An unreachable cluster has status running (RED-32805)** When a cluster is in an unreachable state, the state remains `running` instead of triggering an error.

- **Long cluster names cause routes to be rejected  (RED-25871)** A cluster name longer than 20 characters will result in a rejected route configuration because the host part of the domain name exceeds 63 characters. The workaround is to limit the cluster name to 20 characters or fewer.

- **Cluster CR (REC) errors are not reported after invalid updates (RED-25542)** A cluster CR specification error is not reported if two or more invalid CR resources are updated in sequence.


Redis Enterprise for Kubernetes 7.8.2-6 (Jan 2025) release notes

Summary: Maintenance release to support Redis Enterprise Software version 7.8.2-60.

Highlights

This is a maintenance release to support [Redis Enterprise Software version 7.8.2-60](). For version changes, supported distributions, and known limitations, see the [release notes for 7.8.2-6 (Nov 2024)]().

Downloads

- **Redis Enterprise**: `redislabs/redis:7.8.2-60`
- **Operator**: `redislabs/operator:7.8.2-6`
- **Services Rigger**: `redislabs/k8s-controller:7.8.2-6`
- **OLM operator bundle** : `v7.8.2-6.8`


Redis Enterprise for Kubernetes 7.8.2-6 (Nov 2024) release notes

Summary: Feature release including support for Redis Software 7.8.2 and RHEL9-based images.

New in this release

Enhancements

- Parallel startup and recovery (enabled by default) (RED-117645).
- Azure marketplate deployment (RED-113029)
- Support for [Redis Software 7.8.2-34]().
- Improved upgrade validations for modules and Redis database versions (RED-132197).
- Support for Community Kubernetes 1.31 (RED-13549).
- New minimal roles required to use the log collector (RED-132686).
- Support proxy certificate updates for Active-Active databases (RED-122552).
- Add `directory_timeout_s` field to LDAP configuration (RED-119079).
- Allow configuring port number for replication endpoints in Active-Active databases (RED-113626).

Resolved issues

- Fixed documentation for REAADB `globalConfigurations` field (RED-138727).
- Allow log collector execution without `kubectl` installed (RED-131537).
- Fix recreation issue for rec-bulletin-board config map (RED-130599).
- Avoid deletion of operator config maps created by users (RED-129214).
- Fixed errors shown in bootstrapper logs (RED-125776).
- Limit the number of calls made to Vault (RED-125396).
- Fixed log collector issue with detecting version (RED-121144).

API changes

| **CRD** | **Field** | **Change** | **Description** |
|---|---|---|---|
| REC | `status.CertificatesUpdateStatus` | Rename | Renamed status field and changed the structure |
| REC | `status.state` | Add value to enum  | `runningRollingUpgrade`  |
| REDB | `spec.modulesList` | Field enabled | Don't need to set `ENABLE_ALPHA_FEATURES` to enable. |
| RERC | `spec.apiPort` | Added |  |
| REDB | `redb.upgradeSpec.upgradeModulesToLatest` | Changed default  | Default is now `true` |

Version changes

Breaking changes

#### RHEL9-based images

- As of version 7.8.2-6, Redis Enterprise images are based on Red Hat Enterprise Linux 9 (RHEL9). This means upgrades to 7.8.2-6 require:

- Cluster version of 7.4.2-2 or later.
- Database version 7.2 or later.
- RHEL9 compatible binaries for any modules you need.

See [Upgrade Redis Enterprise for Kubernetes]() for detailed steps to upgrade to 7.8.2-6.

Deprecations

- Ubuntu-based images are no longer supported.
- REDB field `upgradeSpec.upgradeModulesToLatest is deprecated.
- REDB field `spec.modulesList.version` is deprecated.

Supported distributions

The following table shows supported distributions at the time of this release. You can also find this list in [Supported Kubernetes distributions]().

✅ Supported – This distribution is supported for this version of Redis Enterprise Software for Kubernetes.

:warning: Deprecated – This distribution is still supported for this version of Redis Enterprise Software for Kubernetes, but support will be removed in a future release.

❌ End of life – Support for this distribution ended.

Any distribution not listed below is not supported for production workloads.

| **Kubernetes version** | **1.25** | **1.26** | **1.27** | **1.28** | **1.29** | **1.30** | **1.31** |
|---|---|---|---|---|---|---|---|
| **Community Kubernetes** |  |  | ❌ | ✅ | ✅ | ✅ | ✅ |
| **Amazon EKS** |  | ❌ | :warning: | ✅ | ✅ | ✅ |  |
| **Azure AKS** |  |  | :warning: | ✅ | ✅ | ✅ |  |
| **Google GKE** |  |  | ❌ | ✅ | ✅ | ✅ |  |
| **Rancher RKE2** |  | :warning: | ✅ | ✅ |  |  |  |
| **VMware TKG 2.3** |  | :warning: |  |  |  |  |  |
| **VMware TKG 2.4** |  | ✅ | ✅ |  |  |  |  |
| **OpenShift** | **4.12** | **4.13** | **4.14** | **4.15** | **4.16** |  |  |
| **** | ✅ | ✅ | ✅ | ✅ | ✅ |  |  |
| **VMWare TKGI** | **1.16** | **1.17** | **1.18** | **1.19** |  |  |  |
| **** | ❌ | ✅ | ✅ | ✅ |  |  |  |

Downloads

**Redis Enterprise**: `redislabs/redis:7.8.2-34`
**Operator**: `redislabs/operator:7.8.2-6`
**Services Rigger**: `redislabs/k8s-controller:7.8.2-6`
**OLM operator bundle**: `v7.8.2-6.3`

Known limitations

New limitations

- **Only upgrades from 7.4.2-2 and later are supported.** If you are using an earlier version, install 7.4.2-2 before upgrading to 7.8.2-6.

- **When changing the REDB field `spec.modulesList` version might be upgraded to latest even if a different version is specified.** To prevent the upgrade to latest, set  `spec.upgradeSpec.setModuleToLatest` to `false` before upgrading to 7.8.2-6.

Existing limitations

- **Missing endpoint for admission endpoint (rare) (RED-119469)** Restart the operator pod.

- **The REDB "redisVersion" field can’t be used for memcached databases(RED-119152)**

- **PVC expansion is not supported when using Redis on Flash (Auto Tiering) (RED-165770)** Do not enable `enablePersistentVolumeResize` if your REC uses `redisOnFlashSpec` as this will result in conflicts.

- **When modifying the database suffix for an Active-Active database, while the service-rigger is in a terminating state, the services-rigger will delete and create the ingress or route resources in a loop (RED-107687)** Wait until the services rigger pod has finished to terminate it.

- **REAADB changes might fail with "gateway timeout" errors, mostly on OpenShift (RED-103048)** Retry the operation.

- **Creating two databases with the same name directly on Redis Enterprise software will cause the service to be deleted and the database will not be available (RED-99997)** Avoid duplicating database names. Database creation via K8s has validation in place to prevent this.

- **Installing the operator bundle produces warning: `Warning: would violate PodSecurity "restricted: v1.24"` (RED-97381)** Ignore the warning. This issue is documented as benign on official Red Hat documentation.

- **RERC resources must have a unique name (RED-96302)** The string "rec-name"/"rec-namespace" must be different from all other participating clusters in the Active-Active database.

- **Admission is not blocking REAADB with `shardCount` which exceeds license quota (RED-96301)** Fix the problems with the REAADB and reapply.

- **Active-Active controller only supports global database options. Configuration specific to location is not supported (RED-86490)**

- **Active-Active setup removal might keep services or routes undeleted (RED-77752)** Delete services or routes manually if you encounter this problem.

- **`autoUpgrade` set to `true` can cause unexpected bdb upgrades when `redisUpgradePolicy` is set to `true` (RED-72351)** Contact support if your deployment is impacted.

- **Following the previous quick start guide version causes issues with creating an REDB due to unrecognized memory field name (RED-69515)** The workaround is to use the newer (current) revision of Deploy Redis Enterprise Software for Kubernetes.

- **PVC size issues when using decimal value in spec (RED-62132)** Make sure you use integer values for the PVC size.

- **REC might report error states on initial startup (RED-61707)** There is no workaround at this time except to ignore the errors.

- **Hashicorp Vault integration - no support for Gesher (RED-55080)** There is no workaround for this issue. Gesher support has been deprecated.

- **REC clusters fail to start on Kubernetes clusters with unsynchronized clocks (RED-47254)** When REC clusters are deployed on Kubernetes clusters without synchronized clocks, the REC cluster does not start correctly. The fix is to use NTP to synchronize the underlying K8s nodes.

- **Deleting an OpenShift project with an REC deployed may hang (RED-47192)** When an REC cluster is deployed in a project (namespace) and has REDB resources, the REDB resources must be deleted first before the REC can be deleted. Therefore, until the REDB resources are deleted, the project deletion will hang. The fix is to delete the REDB resources first and the REC second. Then, you can delete the project.

- **Clusters must be named 'rec' in OLM-based deployments (RED-39825)** In OLM-deployed operators, the deployment of the cluster will fail if the name is not "rec". When the operator is deployed via the OLM, the security context constraints (scc) are bound to a specific service account name (namely, "rec"). The workaround is to name the cluster "rec".

- **Readiness probe incorrect on failures (RED-39300)** STS Readiness probe does not mark a node as "not ready" when running `rladmin status` on node failure.

- **Internal DNS and Kubernetes DNS may have conflicts (RED-37462)** DNS conflicts are possible between the cluster `mdns_server` and the K8s DNS. This only impacts DNS resolution from within cluster nodes for Kubernetes DNS names.

- **K8s-based 5.4.10 clusters seem to negatively affect existing 5.4.6 clusters (RED-37233)** Upgrade clusters to latest version.

- **Node CPU usage is reported instead of pod CPU usage (RED-36884)** In Kubernetes, the reported node CPU usage is the usage of the Kubernetes worker node hosting the REC pod.

- **An unreachable cluster has status running (RED-32805)** When a cluster is in an unreachable state, the state remains `running` instead of triggering an error.

- **Long cluster names cause routes to be rejected  (RED-25871)** A cluster name longer than 20 characters will result in a rejected route configuration because the host part of the domain name exceeds 63 characters. The workaround is to limit the cluster name to 20 characters or fewer.

- **Cluster CR (REC) errors are not reported after invalid updates (RED-25542)** A cluster CR specification error is not reported if two or more invalid CR resources are updated in sequence.


Redis Enterprise for Kubernetes 7.8.2-6 release notes

Summary: Releases with support for Redis Enterprise Software 7.8.2

Overview

Redis Enterprise for Kubernetes 7.8.2-6 is a feature release including support for Redis Software 7.8.2-2.

Detailed release notes

Breaking changes

The following changes included in this release affect the upgrade process. Please read carefully before upgrading.

RHEL9-based images

- Redis Enterprise images are now based on RHEL9.
- Ubuntu images are no longer supported.

This means upgrades to 7.8.2-6 require:

- Cluster version of 7.4.2-2 or later.
- Database version 7.2 or later.
- RHEL9 compatible binaries for any modules you need.

See [Upgrade Redis Enterprise for Kubernetes]() for detailed steps to upgrade to 7.8.2-6.

Known limitations

New limitations

- **Only upgrades from 7.4.2-2 and later are supported.** If you are using an earlier version, install 7.4.2-2 before upgrading to 7.8.2-6.

- **When changing the REDB field `spec.modulesList` version might be upgraded to latest even if a different version is specified.** To prevent the upgrade to latest, set `spec.upgradeSpec.setModuleToLatest` to `false` before upgrading to 7.8.2-6.

Existing limitations


Redis Enterprise for Kubernetes 7.8.4-8 (Feb 2025) release notes

Summary: Maintenance release to support Redis Enterprise Software version 7.8.4-66.

Overview

This release includes bug fixes, enhancements, and support for [Redis Enterprise Software version 7.8.4-66]().

New in this release

Enhancements

- Support for a read-only file system on Redis Enterprise containers (RED-75139).
- Support for [Redis Enterprise Software version 7.8.4-66]().

Resolved issues

- Fixed log collector handling of STDERR warnings (RED-148292).

API changes

| **CRD** | **Field** | **Change** | **Description** |
|---|---|---|---|
| REC | spec.SecurityContext.readOnlyRootFilesystemPolicy.enabled | Add | Enables the read-only filesystem |

Supported distributions

Downloads

- **Redis Enterprise**: `redislabs/redis:7.8.4-66`
- **Operator**: `redislabs/operator:7.8.4-8`
- **Services Rigger**: `redislabs/k8s-controller:7.8.4-8`
- **OLM operator bundle** : `v7.8.4-8.0`


Redis Enterprise for Kubernetes 7.8.4-9 (March 2025) release notes

Summary: Maintenance release to support Redis Enterprise Software version 7.8.4-95.

Overview

This is a maintenance release to support [Redis Enterprise Software version 7.8.4-95]() and OpenShift 4.17 and 4.18.

For version changes and known limitations, see the [release notes for 7.8.2-6 (Nov 2024)]().

Supported distributions

The following table shows supported distributions at the time of this release. You can also find this list in [Supported Kubernetes distributions]().

✅ Supported – This distribution is supported for this version of Redis Enterprise Software for Kubernetes.

:warning: Deprecated – This distribution is still supported for this version of Redis Enterprise Software for Kubernetes, but support will be removed in a future release.

❌ End of life – Support for this distribution ended.

Any distribution not listed below is not supported for production workloads.

| **Kubernetes version** | **1.25** | **1.26** | **1.27** | **1.28** | **1.29** | **1.30** | **1.31** |
|---|---|---|---|---|---|---|---|
| **Community Kubernetes** |  |  | ❌ | ✅ | ✅ | ✅ | ✅ |
| **Amazon EKS** |  | ❌ | :warning: | ✅ | ✅ | ✅ |  |
| **Azure AKS** |  |  | :warning: | ✅ | ✅ | ✅ |  |
| **Google GKE** |  |  | ❌ | ✅ | ✅ | ✅ |  |
| **Rancher RKE2** |  | :warning: | ✅ | ✅ |  |  |  |
| **VMware TKG 2.3** |  | :warning: |  |  |  |  |  |
| **VMware TKG 2.4** |  | ✅ | ✅ |  |  |  |  |
| **OpenShift** | **4.12** | **4.13** | **4.14** | **4.15** | **4.16** | **4.17** | **4.18** |
| **** | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ |
| **VMWare TKGI** | **1.16** | **1.17** | **1.18** | **1.19** |  |  |  |
| **** | ❌ | ✅ | ✅ | ✅ |  |  |  |

Downloads

- **Redis Enterprise**: `redislabs/redis:7.8.4-95`
- **Operator**: `redislabs/operator:7.8.4-9`
- **Services Rigger**: `redislabs/k8s-controller:7.8.4-9`
- **OLM operator bundle** : `v7.8.4-9.0`


Redis Enterprise for Kubernetes 7.8.4 release notes

Summary: Releases with support for Redis Enterprise Software 7.8.4

Overview

Redis Enterprise for Kubernetes 7.8.4-8 includes bug fixes, enhancements, and support for [Redis Enterprise Software version 7.8.4]().

Detailed release notes

Breaking changes

RHEL9-based images

- As of version 7.8.2-6, Redis Enterprise images are based on Red Hat Enterprise Linux 9 (RHEL9). This means upgrades to 7.8.2-6 require:

- Cluster version of 7.4.2-2 or later.
- Database version 7.2 or later.
- RHEL9 compatible binaries for any modules you need.

See [Upgrade Redis Enterprise for Kubernetes]() for detailed steps to upgrade to 7.8.4-8.

Deprecations

- Ubuntu-based images are no longer supported.
- REDB field `upgradeSpec.upgradeModulesToLatest is deprecated.
- REDB field `spec.modulesList.version` is deprecated.

Known limitations

New limitations

- **Specifying `databasePort` causes issues with REAADB synchronization. (RED-149374)**

Existing limitations

- **Only upgrades from 7.4.2-2 and later are supported.** If you are using an earlier version, install 7.4.2-2 before upgrading to 7.8.2-6 or later.

- **When changing the REDB field `spec.modulesList`, version might be upgraded to latest, even if a different version is specified.** To prevent the upgrade to latest, set  `spec.upgradeSpec.setModuleToLatest` to `false` before upgrading to 7.8.2-6.

- **Missing endpoint for admission endpoint (rare) (RED-119469)** Restart the operator pod.

- **The REDB "redisVersion" field can’t be used for memcached databases(RED-119152)**

- **When modifying the database suffix for an Active-Active database, while the service-rigger is in a terminating state, the services-rigger will delete and create the ingress or route resources in a loop (RED-107687)** Wait until the services rigger pod has finished to terminate it.

- **REAADB changes might fail with "gateway timeout" errors, mostly on OpenShift (RED-103048)** Retry the operation.

- **Creating two databases with the same name directly on Redis Enterprise software will cause the service to be deleted and the database will not be available (RED-99997)** Avoid duplicating database names. Database creation via K8s has validation in place to prevent this.

- **Installing the operator bundle produces warning: `Warning: would violate PodSecurity "restricted: v1.24"` (RED-97381)** Ignore the warning. This issue is documented as benign on official Red Hat documentation.

- **RERC resources must have a unique name (RED-96302)** The string "rec-name"/"rec-namespace" must be different from all other participating clusters in the Active-Active database.

- **Admission is not blocking REAADB with `shardCount` which exceeds license quota (RED-96301)** Fix the problems with the REAADB and reapply.

- **Active-Active controller only supports global database options. Configuration specific to location is not supported (RED-86490)**

- **Active-Active setup removal might keep services or routes undeleted (RED-77752)** Delete services or routes manually if you encounter this problem.

- **`autoUpgrade` set to `true` can cause unexpected bdb upgrades when `redisUpgradePolicy` is set to `true` (RED-72351)** Contact support if your deployment is impacted.

- **Following the previous quick start guide version causes issues with creating an REDB due to unrecognized memory field name (RED-69515)** The workaround is to use the newer (current) revision of Deploy Redis Enterprise Software for Kubernetes.

- **PVC size issues when using decimal value in spec (RED-62132)** Make sure you use integer values for the PVC size.

- **REC might report error states on initial startup (RED-61707)** There is no workaround at this time except to ignore the errors.

- **Hashicorp Vault integration - no support for Gesher (RED-55080)** There is no workaround for this issue. Gesher support has been deprecated.

- **REC clusters fail to start on Kubernetes clusters with unsynchronized clocks (RED-47254)** When REC clusters are deployed on Kubernetes clusters without synchronized clocks, the REC cluster does not start correctly. The fix is to use NTP to synchronize the underlying K8s nodes.

- **Deleting an OpenShift project with an REC deployed may hang (RED-47192)** When an REC cluster is deployed in a project (namespace) and has REDB resources, the REDB resources must be deleted first before the REC can be deleted. Therefore, until the REDB resources are deleted, the project deletion will hang. The fix is to delete the REDB resources first and the REC second. Then, you can delete the project.

- **Clusters must be named 'rec' in OLM-based deployments (RED-39825)** In OLM-deployed operators, the deployment of the cluster will fail if the name is not "rec". When the operator is deployed via the OLM, the security context constraints (scc) are bound to a specific service account name (namely, "rec"). The workaround is to name the cluster "rec".

- **Readiness probe incorrect on failures (RED-39300)** STS Readiness probe does not mark a node as "not ready" when running `rladmin status` on node failure.

- **Internal DNS and Kubernetes DNS may have conflicts (RED-37462)** DNS conflicts are possible between the cluster `mdns_server` and the K8s DNS. This only impacts DNS resolution from within cluster nodes for Kubernetes DNS names.

- **K8s-based 5.4.10 clusters seem to negatively affect existing 5.4.6 clusters (RED-37233)** Upgrade clusters to latest version.

- **Node CPU usage is reported instead of pod CPU usage (RED-36884)** In Kubernetes, the reported node CPU usage is the usage of the Kubernetes worker node hosting the REC pod.

- **An unreachable cluster has status running (RED-32805)** When a cluster is in an unreachable state, the state remains `running` instead of triggering an error.

- **Long cluster names cause routes to be rejected  (RED-25871)** A cluster name longer than 20 characters will result in a rejected route configuration because the host part of the domain name exceeds 63 characters. The workaround is to limit the cluster name to 20 characters or fewer.

- **Cluster CR (REC) errors are not reported after invalid updates (RED-25542)** A cluster CR specification error is not reported if two or more invalid CR resources are updated in sequence.


Redis Enterprise for Kubernetes 7.8.6-1 (April 2025) release notes

Summary: A maintenance release that includes support for Redis Software 7.8.6-36.

New in the release

Redis Enterprise for Kubernetes 7.8.6-1 (April 2025) is a maintenance release that includes support for [Redis Software 7.8.6-36]().

For supported distributions, known limitations, and API changes, see [Redis Enterprise for Kubernetes 7.8.6-1 March 2025 release notes]().

Downloads

- **Redis Enterprise**: `redislabs/redis:7.8.6-36`
- **Operator**: `redislabs/operator:7.8.6-1`
- **Services Rigger**: `redislabs/k8s-controller:7.8.6-1`
- **OLM operator bundle** : `v7.8.6-1.1`

Known limitations

See [7.8.6 releases]() for information on known limitations.


Redis Enterprise for Kubernetes 7.8.6-1 (March 2025) release notes

Summary: Feature release including enhancements, bug fixes, platform updates, and support for Redis Software 7.8.6-13

New in the release

Redis Enterprise for Kubernetes 7.8.6-1 is a feature release that includes enhancements, bug fixes, platform updates, and support for [Redis Software 7.8.6-13]().

This release also includes the ability to [install the operator using Helm]().

Support for Helm is currently in public preview and is not supported on production workloads. Only new installations of the Redis operator are supported at this time.

Enhancements

- Added support for [Redis Software 7.8.6-13]().
- Updated supported Kubernetes distributions
- DatabaseServicePortPolicy allows use of the default Redis port (6379) for database services.
- Added additional license fields to the REC status.
- Added validation to prevent unsupported changes to podDisruptionBudget.

Resolved issues

- Fixed Sonarcube findings in the log collector (RED-129297).
- Fixed upgrade failure due to update of the nodeSelector during the upgrade (RED-138445).
- Fixed issues with Vault plugin connections to Redis Enterprise (RED-139352 RED-144637).
- Fixed operator crash when a namespace is labeled with a specific label (RED-140344).
- Fixed failure in Services Rigger when a database uses port 10250 (RED-142673).
- Reduced CPU priority of the health_check.py script to ensure availability (RED-144360).
- Fixed broken use case for customizing the Active-Active port. (RED-149374).
- Fixed API reference for REDB properties (RED-151195).
- Fixed operator CVE-2024-24786 (RED-151873).
- Fixed wrong image tag for OpenShift example YAML (RED-152022).

API changes

| **CRD** | **Field** | **Change** | **Description** |
|---|---|---|---|
| REAADB | `spec.externalReplicationPort` | ADD | Specifies the replication endpoint port number for users who use LoadBalancers to synchronize Active-Active replicas and must provide the port that the LoadBalancer listens on. |
| REC | `status.shardsUsage` | ADD | Total number of shards (both RAM and flash) currently in use under this license. |
| REC | `status.flashShards` | ADD | Number of flash shards currently in use under this license. |
| REC | `status.flashShardsLimit` | ADD | Number of flash shards allowed under this license. |
| REC | `status.ramShards` | ADD | Number of RAM shards currently in use under this license. |
| REC | `status.ramShardsLimit` | ADD | Number of RAM shards allowed under this license. |
| REC | `spec.podSecurityPolicyName` | REMOVE | Not supported anymore by supported Kubernetes versions. |
| REC | `spec.databaseServicePortPolicy` | ADD | Specifies how to determine service ports for REDB services. Defaults to DatabasePortForward if not set. DatabasePortForward - The service port will be the same as the database port. RedisDefaultPort - The service port will be the default Redis port (6379).

Breaking changes

Customers who use load balancers for Active-Active replication endpoints and rely on the change introduced in RED-113626 (or the workaround described in the ticket) must set the spec.externalReplicationPort field in REAADB after upgrading. Otherwise, replication will fail (RED-149374).

RHEL9-based image

As of version 7.8.2-6, Redis Enterprise images are based on Red Hat Enterprise Linux 9 (RHEL9). This means upgrades require:

- [Cluster version of 7.4.2-2 or later](https://redis.io/docs/latest/operate/kubernetes/7.4.6/upgrade/).
- Database version 7.2 or later.
- RHEL9 compatible binaries for any modules you need.

For detailed steps, see the relevant upgrade page:

- [OpenShift CLI]()
- [OpenShift OperatorHub]()
- [Kubernetes]()

Supported distributions

The following table shows supported distributions at the time of this release. You can also find this list in [Supported Kubernetes distributions]().

✅ Supported – This distribution is supported for this version of Redis Enterprise Software for Kubernetes.

:warning: Deprecated – This distribution is still supported for this version of Redis Enterprise Software for Kubernetes, but support will be removed in a future release.

❌ End of life – Support for this distribution ended.

Any distribution not listed below is not supported for production workloads.

| Kubernetes version | **1.26** | **1.27** | **1.28** | **1.29** | **1.30** | **1.31** | **1.32** |
|---|---|---|---|---|---|---|---|
|  |  |  |  |  |  |  |  |
| **Community K8s** |  |  | ❌ | ❌ | ✅ | ✅ | ✅ |
| **Amazon EKS** |  |  | ❌ | :warning: | ✅ | ✅ | ✅ |
| **Azure AKS** |  |  | ❌ | :warning: | ✅ | ✅ | ✅ |
| **Google GKE** |  |  | ❌ | :warning: | ✅ | ✅ | ✅ |
| **Rancher** |  | ✅ | ✅ | ✅ |  |  |  |
| **VMware TKG 2.4** | :warning: | :warning: |  |  |  |  |  |
| **OpenShift** | **4.13** | **4.14** | **4.15** | **4.16** | **4.17** | **4.18** |  |
|  | :warning: | :warning: | ✅ | ✅ | ✅ |  |  |
| **VMware TKGI** | **1.16 | **1.17 | **1.18 | **1.19 | **1.2 |  |  |
|  |  | :warning: | :warning: | ✅ | ✅ |  |  |

Downloads

- **Redis Enterprise**: `redislabs/operator:7.8.6-13`
- **Operator**: `redislabs/redis:7.8.6-1`
- **Services Rigger**: `redislabs/k8s-controller:7.8.6-1`
- **OLM operator bundle** : `v7.8.6-1.0`

Known limitations


Redis Enterprise for Kubernetes 7.8.6-1 (May 2025) release notes

Summary: A maintenance release that includes support for Redis Software 7.8.6-60.

Overview

Redis Enterprise for Kubernetes 7.8.6-1 (May 2025) is a maintenance release that includes support for [Redis Software 7.8.6-60]().

For supported distributions, known limitations, and API changes, see [Redis Enterprise for Kubernetes 7.8.6-1 March 2025 release notes]().

Downloads

- **Redis Enterprise**: `redislabs/redis:7.8.6-60`
- **Operator**: `redislabs/operator:7.8.6-1`
- **Services Rigger**: `redislabs/k8s-controller:7.8.6-1`
- **OLM operator bundle** : `v7.8.6-1.2`

Known limitations


Redis Enterprise for Kubernetes 7.8.6-11 (February 2026) release notes

Summary: A maintenance release that includes support for Redis Software 7.8.6-253.

Overview

Redis Enterprise for Kubernetes 7.8.6-11 (February 2026) is a maintenance release that includes support for [Redis Software 7.8.6-253]().

For supported distributions, known limitations, and API changes, see [Redis Enterprise for Kubernetes 7.8.6-1 March 2025 release notes]().

Downloads

- **Redis Enterprise**: `redislabs/redis:7.8.6-253`
- **Operator**: `redislabs/operator:7.8.6-11`
- **Services Rigger**: `redislabs/k8s-controller:7.8.6-11`
- **OLM operator bundle** : `v7.8.6-11.0`

Known limitations


Redis Enterprise for Kubernetes 7.8.6-13 (March 2026) release notes

Summary: A maintenance release that includes support for Redis Software 7.8.6-256.

Overview

Redis Enterprise for Kubernetes 7.8.6-13 (March 2026) is a maintenance release that includes support for [Redis Software 7.8.6-256]().

For supported distributions, known limitations, and API changes, see [Redis Enterprise for Kubernetes 7.8.6-1 March 2025 release notes]().

Downloads

- **Redis Enterprise**: `redislabs/redis:7.8.6-256`
- **Operator**: `redislabs/operator:7.8.6-13`
- **Services Rigger**: `redislabs/k8s-controller:7.8.6-13`
- **OLM operator bundle** : `v7.8.6-13.0`

Known limitations


Redis Enterprise for Kubernetes 7.8.6-2 (June 2025) release notes

Summary: A maintenance release that includes support for Redis Software 7.8.6-95.

Overview

Redis Enterprise for Kubernetes 7.8.6-2 (June 2025) is a maintenance release that includes support for [Redis Software 7.8.6-95]().

For supported distributions, known limitations, and API changes, see [Redis Enterprise for Kubernetes 7.8.6-1 March 2025 release notes]().

Downloads

- **Redis Enterprise**: `redislabs/redis:7.8.6-95`
- **Operator**: `redislabs/operator:7.8.6-2`
- **Services Rigger**: `redislabs/k8s-controller:7.8.6-2`
- **OLM operator bundle** : `v7.8.6-2.2`

Known limitations

See [7.8.6 releases]() for information on known limitations.


Redis Enterprise for Kubernetes 7.8.6-3 (June 2025) release notes

Summary: A maintenance release that includes support for Redis Software 7.8.6-119.

Overview

Redis Enterprise for Kubernetes 7.8.6-3 (June 2025) is a maintenance release that includes support for [Redis Software 7.8.6-119]().

For supported distributions, known limitations, and API changes, see [Redis Enterprise for Kubernetes 7.8.6-1 March 2025 release notes]().

Downloads

- **Redis Enterprise**: `redislabs/redis:7.8.6-119`
- **Operator**: `redislabs/operator:7.8.6-3`
- **Services Rigger**: `redislabs/k8s-controller:7.8.6-3`
- **OLM operator bundle** : `v7.8.6-3.2`

Known limitations


Redis Enterprise for Kubernetes 7.8.6-5 (August 2025) release notes

Summary: A maintenance release that includes support for Redis Software 7.8.6-152.

Overview

Redis Enterprise for Kubernetes 7.8.6-5 (August 2025) is a maintenance release that includes support for [Redis Software 7.8.6-152]().

For supported distributions, known limitations, and API changes, see [Redis Enterprise for Kubernetes 7.8.6-1 March 2025 release notes]().

Downloads

- **Redis Enterprise**: `redislabs/redis:7.8.6-152`
- **Operator**: `redislabs/operator:7.8.6-5`
- **Services Rigger**: `redislabs/k8s-controller:7.8.6-5`
- **OLM operator bundle** : `v7.8.6-5.1`

Known limitations


Redis Enterprise for Kubernetes 7.8.6-8 (October 2025) release notes

Summary: A maintenance release that includes support for Redis Software 7.8.6-207.

Overview

Redis Enterprise for Kubernetes 7.8.6-8 (October 2025) is a maintenance release that includes support for [Redis Software 7.8.6-207]().

For supported distributions, known limitations, and API changes, see [Redis Enterprise for Kubernetes 7.8.6-1 March 2025 release notes]().

Downloads

- **Redis Enterprise**: `redislabs/redis:7.8.6-207`
- **Operator**: `redislabs/operator:7.8.6-8`
- **Services Rigger**: `redislabs/k8s-controller:7.8.6-8`
- **OLM operator bundle** : `v7.8.6-8.1`

Known limitations


Redis Enterprise for Kubernetes 7.8.6 release notes

Summary: Releases with support for Redis Enterprise Software 7.8.6

Overview

Redis Enterprise for Kubernetes 7.8.6 includes bug fixes, enhancements, and support for Redis Enterprise Software. The latest release is 7.8.6-13 with support for Redis Enterprise Software version 7.8.6-256.

Detailed release notes

Breaking changes

Customers who use load balancers for Active-Active replication endpoints and rely on the change introduced in RED-113626 (or the workaround described in the ticket) must set the spec.externalReplicationPort field in REAADB after upgrading. Otherwise, replication will fail (RED-149374).

RHEL9-based image

As of version 7.8.2-6, Redis Enterprise images are based on Red Hat Enterprise Linux 9 (RHEL9). This means upgrades require:

- [Cluster version of 7.4.2-2 or later](https://redis.io/docs/latest/operate/kubernetes/7.4.6/upgrade/).
- Database version 7.2 or later.
- RHEL9 compatible binaries for any modules you need.

For detailed steps, see the relevant upgrade page:

- [OpenShift CLI]()
- [OpenShift OperatorHub]()
- [Kubernetes]()

Known limitations

- **Only upgrades from 7.4.2-2 and later are supported.** If you are using an earlier version, install 7.4.2-2 before upgrading to 7.8.2-6 or later.

- **When changing the REDB field `spec.modulesList`, version might be upgraded to latest, even if a different version is specified.** To prevent the upgrade to latest, set  `spec.upgradeSpec.setModuleToLatest` to `false` before upgrading to 7.8.2-6.

- **Missing endpoint for admission endpoint (rare) (RED-119469)** Restart the operator pod.

- **The REDB "redisVersion" field can’t be used for memcached databases(RED-119152)**

- **When modifying the database suffix for an Active-Active database, while the service-rigger is in a terminating state, the services-rigger will delete and create the ingress or route resources in a loop (RED-107687)** Wait until the services rigger pod has finished to terminate it.

- **REAADB changes might fail with "gateway timeout" errors, mostly on OpenShift (RED-103048)** Retry the operation.

- **Creating two databases with the same name directly on Redis Enterprise software will cause the service to be deleted and the database will not be available (RED-99997)** Avoid duplicating database names. Database creation via K8s has validation in place to prevent this.

- **Installing the operator bundle produces warning: `Warning: would violate PodSecurity "restricted: v1.24"` (RED-97381)** Ignore the warning. This issue is documented as benign on official Red Hat documentation.

- **RERC resources must have a unique name (RED-96302)** The string "rec-name"/"rec-namespace" must be different from all other participating clusters in the Active-Active database.

- **Admission is not blocking REAADB with `shardCount` which exceeds license quota (RED-96301)** Fix the problems with the REAADB and reapply.

- **Active-Active controller only supports global database options. Configuration specific to location is not supported (RED-86490)**

- **Active-Active setup removal might keep services or routes undeleted (RED-77752)** Delete services or routes manually if you encounter this problem.

- **`autoUpgrade` set to `true` can cause unexpected bdb upgrades when `redisUpgradePolicy` is set to `true` (RED-72351)** Contact support if your deployment is impacted.

- **Following the previous quick start guide version causes issues with creating an REDB due to unrecognized memory field name (RED-69515)** The workaround is to use the newer (current) revision of Deploy Redis Enterprise Software for Kubernetes.

- **PVC size issues when using decimal value in spec (RED-62132)** Make sure you use integer values for the PVC size.

- **REC might report error states on initial startup (RED-61707)** There is no workaround at this time except to ignore the errors.

- **Hashicorp Vault integration - no support for Gesher (RED-55080)** There is no workaround for this issue. Gesher support has been deprecated.

- **REC clusters fail to start on Kubernetes clusters with unsynchronized clocks (RED-47254)** When REC clusters are deployed on Kubernetes clusters without synchronized clocks, the REC cluster does not start correctly. The fix is to use NTP to synchronize the underlying K8s nodes.

- **Deleting an OpenShift project with an REC deployed may hang (RED-47192)** When an REC cluster is deployed in a project (namespace) and has REDB resources, the REDB resources must be deleted first before the REC can be deleted. Therefore, until the REDB resources are deleted, the project deletion will hang. The fix is to delete the REDB resources first and the REC second. Then, you can delete the project.

- **Clusters must be named 'rec' in OLM-based deployments (RED-39825)** In OLM-deployed operators, the deployment of the cluster will fail if the name is not "rec". When the operator is deployed via the OLM, the security context constraints (scc) are bound to a specific service account name (namely, "rec"). The workaround is to name the cluster "rec".

- **Readiness probe incorrect on failures (RED-39300)** STS Readiness probe does not mark a node as "not ready" when running `rladmin status` on node failure.

- **Internal DNS and Kubernetes DNS may have conflicts (RED-37462)** DNS conflicts are possible between the cluster `mdns_server` and the K8s DNS. This only impacts DNS resolution from within cluster nodes for Kubernetes DNS names.

- **K8s-based 5.4.10 clusters seem to negatively affect existing 5.4.6 clusters (RED-37233)** Upgrade clusters to latest version.

- **Node CPU usage is reported instead of pod CPU usage (RED-36884)** In Kubernetes, the reported node CPU usage is the usage of the Kubernetes worker node hosting the REC pod.

- **An unreachable cluster has status running (RED-32805)** When a cluster is in an unreachable state, the state remains `running` instead of triggering an error.

- **Long cluster names cause routes to be rejected  (RED-25871)** A cluster name longer than 20 characters will result in a rejected route configuration because the host part of the domain name exceeds 63 characters. The workaround is to limit the cluster name to 20 characters or fewer.

- **Cluster CR (REC) errors are not reported after invalid updates (RED-25542)** A cluster CR specification error is not reported if two or more invalid CR resources are updated in sequence.


Redis Enterprise for Kubernetes 8.0.10-21 (February 2026) release notes

Summary: Feature release with OSS Cluster API support for external clients, ARM architecture support, and Redis Software 8.0.10-64.

Overview

Redis Enterprise for Kubernetes 8.0.10-21 is a feature release that supports [Redis Software 8.0.10-64
]() and includes new features and enhancements.

Highlights

- OSS Cluster API support for external clients
- ARM architecture support
- Redis Software 8.0.10-64 support

Enhancements

- Added OSS Cluster API support for external clients <!--RED-51898-->
- Added ARM architecture support <!--RED-164742-->
- Added Vault secret support for user-defined modules <!--RED-178449-->
- Added `extraLabels` injection to resources created by the services rigger <!--RED-180274-->
- Added `clusterCredentialSecretName` customization with Kubernetes secrets <!--RED-180513-->
- REC username default value now derives from the cluster credentials secret <!--RED-180515-->
- Added Kubernetes 1.35 support on select platforms <!--RED-181443-->

When you pull images from container registries such as Docker Hub, ARM support is transparent. The registry automatically serves the correct image based on the node architecture (AMD64 or ARM64).

Resolved issues

- Fixed invalid `containerStatuses` indexing caused by incorrect order assumption <!--RED-175259-->
- Removed unnecessary update calls from the services rigger to load balancers <!--RED-176881-->
- Fixed multiple security issues

API changes

| **CRD** | **Field** | **Change** | **Description** |
|---|---|---|---|
| REDB | `spec.ossClusterSettings` | Added | Additional OSS cluster mode settings. |
| REDB | `spec.ossClusterSettings.enableExternalAccess` | Added | Toggles whether this database supports external access in OSS cluster mode. When enabled, advertised database topology includes the external endpoints for the Redis Enterprise nodes hosting the database shards. The external access mechanism (such as LoadBalancer services) is configured using the `ossClusterSettings.externalAccessType` field of the RedisEnterpriseCluster. When external access is enabled, the corresponding database secret will have the list of primary shard IPs in the `oss_startup_nodes` field. |

Supported distributions

The following table shows supported distributions at the time of this release. You can also find this list in [Supported Kubernetes distributions]().

✅ **Supported** – This distribution is supported for this version of Redis Enterprise Software for Kubernetes.

:warning: **Deprecated** – This distribution is still supported for this version of Redis Enterprise Software for Kubernetes, but support will be removed in a future release.

❌ **End of life** – Support for this distribution ended.

Any distribution not listed in the table is not supported for production workloads.

| Kubernetes version | **1.30** | **1.31** | **1.32** | **1.33** | **1.34** | **1.35** |
|---|---|---|---|---|---|---|
| **Community K8s** |  |  | :warning: | ✅ | ✅ | ✅ |
| **Amazon EKS** |  |  | :warning: | ✅ | ✅ |  |
| **Azure EKS** |  |  | :warning: | ✅ | ✅ |  |
| **Google GKE** |  |  | :warning: | ✅ | ✅ | ✅ |
| **Rancher REK2** |  | ❌ | :warning: | ✅ | ✅ |  |
| **VMware VKS** |  |  | ✅ |  |  |  |
|  |  |  |  |  |  |  |
| **OpenShift** | **4.17** | **4.18** | **4.19** | **4.20** |  |  |
| --- | --- | --- | --- | --- | --- |  |
|  | :warning: | ✅ | ✅ | ✅ |  |  |
|  |  |  |  |  |  |  |
| **VMware TKGI** | **1.21** | **1.22** | **1.23** |  |  |  |
| --- | --- | --- | --- | --- | --- |  |
|  | :warning: | ✅ | ✅ |  |  |  |

Downloads

- **Redis Enterprise**: `redislabs/redis:8.0.10-64`
- **Operator**: `redislabs/operator:8.0.10-21`
- **Services Rigger**: `redislabs/k8s-controller:8.0.10-21`
- **Callhome client**: `redislabs/re-call-home-client:8.0.10-21`

Openshift downloads

- **Redis Enterprise OLM operator bundle**: `8.0.10-21.0`
- **Call Home Client**: `redislabs/call-home-client:8.0.10-21`

Known limitations

New limitations

- **SSO configuration does not work with IPv6 or dual-stack (IPv4/IPv6) clusters.** <!--RED-180550-->

Existing limitations

- **Upgrades from versions earlier than 7.4.2-2 are not supported.** If you use an earlier version, upgrade to 7.4.2-2 before upgrading to 8.0.10-21.

- **Missing endpoint for admission endpoint (rare). (RED-119469)** Restart the operator pod.

- **The REDB `redisVersion` field cannot be used for memcached databases. (RED-119152)**

- **Modifying the database suffix for an Active-Active database while the services rigger is terminating causes a loop. (RED-107687)** The services rigger deletes and recreates ingress or route resources repeatedly. Wait for the services rigger pod to finish terminating before modifying the suffix.

- **REAADB changes might fail with "gateway timeout" errors, especially on OpenShift. (RED-103048)** Retry the operation.

- **Creating two databases with the same name in the Redis Enterprise Cluster Manager UI deletes the service and makes the database unavailable. (RED-99997)** Avoid duplicate database names. The admission controller prevents duplicate names when you create databases through the Kubernetes operator.

- **Installing the operator bundle produces the warning `Warning: would violate PodSecurity "restricted: v1.24"`. (RED-97381)** Ignore this warning. Red Hat documentation identifies this issue as benign.

- **RERC resources must have a unique name. (RED-96302)** The `rec-name/rec-namespace` string must differ from all other participating clusters in the Active-Active database.

- **Admission does not block REAADB resources with a `shardCount` that exceeds the license quota. (RED-96301)** Correct the REAADB configuration and reapply.

- **The Active-Active controller supports only global database options. (RED-86490)** Location-specific configuration is not supported.

- **Removing an Active-Active setup might leave services or routes undeleted. (RED-77752)** Delete the services or routes manually.

- **Setting `autoUpgrade` to `true` can cause unexpected database upgrades when `redisUpgradePolicy` is also `true`. (RED-72351)** Contact support if your deployment is affected.

- **Using the previous quick start guide causes REDB creation issues due to an unrecognized memory field name. (RED-69515)** Use the current version of the Deploy Redis Enterprise Software for Kubernetes guide.

- **PVC size does not work with decimal values. (RED-62132)** Use integer values for the PVC size.

- **REC might report error states on initial startup. (RED-61707)** No workaround exists. Ignore the errors.

- **HashiCorp Vault integration does not support Gesher. (RED-55080)** No workaround exists. Gesher support is deprecated.

- **REC clusters fail to start on Kubernetes clusters with unsynchronized clocks. (RED-47254)** Use NTP to synchronize the underlying Kubernetes nodes.

- **Deleting an OpenShift project with a deployed REC might hang. (RED-47192)** When an REC cluster is deployed in a project (namespace) with REDB resources, you must delete the REDB resources before deleting the REC. The project deletion hangs until you delete the REDB resources. Delete the REDB resources first, then delete the REC, and then delete the project.

- **Clusters must be named "rec" in OLM-based deployments. (RED-39825)** When you deploy the operator through OLM, the security context constraints (SCC) are bound to a specific service account name ("rec"). The deployment fails if the cluster has a different name.

- **Readiness probe does not correctly report failures. (RED-39300)** The StatefulSet readiness probe does not mark a node as "not ready" when running `rladmin status` on node failure.

- **Internal DNS and Kubernetes DNS might conflict. (RED-37462)** DNS conflicts can occur between the cluster `mdns_server` and Kubernetes DNS. This affects only DNS resolution from within cluster nodes for Kubernetes DNS names.

- **Kubernetes-based 5.4.10 clusters might negatively affect existing 5.4.6 clusters. (RED-37233)** Upgrade your clusters to the latest version.

- **Node CPU usage is reported instead of pod CPU usage. (RED-36884)** The reported CPU usage is for the Kubernetes worker node hosting the REC pod, not the pod itself.

- **An unreachable cluster shows status as running. (RED-32805)** When a cluster is unreachable, the status remains `running` instead of showing an error.

- **Long cluster names cause routes to be rejected. (RED-25871)** A cluster name longer than 20 characters causes route rejection because the host part of the domain name exceeds 63 characters. Limit the cluster name to 20 characters or fewer.

- **Cluster CR (REC) errors are not reported after invalid updates. (RED-25542)** A cluster CR specification error is not reported if you update two or more invalid CR resources in sequence.


Redis Enterprise for Kubernetes 8.0.10-22 (February 2026) release notes

Highlights

This is a maintenance release to support Redis Enterprise Software version 8.0.10-76. For version changes, supported distributions, and known limitations, see the [release notes for 8.0.10-21 (February 2026)]().

Downloads

- **Redis Enterprise**: `redislabs/redis:8.0.10-76`
- **Operator**: `redislabs/operator:8.0.10-22`
- **Services Rigger**: `redislabs/k8s-controller:8.0.10-22`
- **Callhome client**: `redislabs/re-call-home-client:8.0.10-22`

Openshift downloads

- **OLM operator bundle**: `8.0.10-22.0`
- **Call Home Client**: `redislabs/call-home-client:8.0.10-22`

Known limitations

See [8.0.10 releases]() for information on known limitations.


Redis Enterprise for Kubernetes 8.0.10-23 (February 2026) release notes

Highlights

This is a maintenance release to support Redis Enterprise Software version 8.0.10-81. For version changes, supported distributions, and known limitations, see the [release notes for 8.0.10-21 (February 2026)]().

Downloads

- **Redis Enterprise**: `redislabs/redis:8.0.10-81`
- **Operator**: `redislabs/operator:8.0.10-23`
- **Services Rigger**: `redislabs/k8s-controller:8.0.10-23`
- **Callhome client**: `redislabs/re-call-home-client:8.0.10-23`

Openshift downloads

- **OLM operator bundle**: `8.0.10-23.0`
- **Call Home Client**: `redislabs/call-home-client:8.0.10-23`

Known limitations


Redis Enterprise for Kubernetes 8.0.10 release notes

Summary: Releases with support for Redis Enterprise Software 8.0.10

Overview

Redis Enterprise for Kubernetes 8.0.10 includes bug fixes, enhancements, and support for Redis Enterprise Software 8.0.10. The latest release is 8.0.10-23 with support for Redis Enterprise Software version 8.0.10-81.

Detailed release notes

Known limitations

New limitations

- **SSO configuration doesn't work with IPv6 or dual stack (IPv4/IPv6) clusters.** <!--RED-180550-->

Existing limitations

- **Only upgrades from 7.4.2-2 and later are supported.** If you are using an earlier version, install 7.4.2-2 before upgrading to 8.0.10-21.

- **Missing endpoint for admission endpoint (rare) (RED-119469)** Restart the operator pod.

- **The REDB "redisVersion" field can't be used for memcached databases (RED-119152)**

- **When modifying the database suffix for an Active-Active database, while the service-rigger is in a terminating state, the services-rigger will delete and create the ingress or route resources in a loop (RED-107687)** Wait until the services rigger pod has finished to terminate it.

- **REAADB changes might fail with "gateway timeout" errors, mostly on OpenShift (RED-103048)** Retry the operation.

- **Creating two databases with the same name directly in the Redis Enterprise cluster manager UI will cause the service to be deleted and the database will not be available (RED-99997)** Avoid duplicating database names. The admission controller prevents duplicate database names when databases are created via the Kubernetes operator.

- **Installing the operator bundle produces warning: `Warning: would violate PodSecurity "restricted: v1.24"` (RED-97381)** Ignore the warning. This issue is documented as benign on official Red Hat documentation.

- **RERC resources must have a unique name (RED-96302)** The string "rec-name"/"rec-namespace" must be different from all other participating clusters in the Active-Active database.

- **Admission is not blocking REAADB with `shardCount` which exceeds license quota (RED-96301)** Fix the problems with the REAADB and reapply.

- **Active-Active controller only supports global database options. Configuration specific to location is not supported (RED-86490)**

- **Active-Active setup removal might keep services or routes undeleted (RED-77752)** Delete services or routes manually if you encounter this problem.

- **`autoUpgrade` set to `true` can cause unexpected bdb upgrades when `redisUpgradePolicy` is set to `true` (RED-72351)** Contact support if your deployment is impacted.

- **Following the previous quick start guide version causes issues with creating an REDB due to unrecognized memory field name (RED-69515)** The workaround is to use the newer (current) revision of Deploy Redis Enterprise Software for Kubernetes.

- **PVC size issues when using decimal value in spec (RED-62132)** Make sure you use integer values for the PVC size.

- **REC might report error states on initial startup (RED-61707)** There is no workaround at this time except to ignore the errors.

- **Hashicorp Vault integration - no support for Gesher (RED-55080)** There is no workaround for this issue. Gesher support has been deprecated.

- **REC clusters fail to start on Kubernetes clusters with unsynchronized clocks (RED-47254)** When REC clusters are deployed on Kubernetes clusters without synchronized clocks, the REC cluster does not start correctly. The fix is to use NTP to synchronize the underlying K8s nodes.

- **Deleting an OpenShift project with an REC deployed may hang (RED-47192)** When an REC cluster is deployed in a project (namespace) and has REDB resources, the REDB resources must be deleted first before the REC can be deleted. Therefore, until the REDB resources are deleted, the project deletion will hang. The fix is to delete the REDB resources first and the REC second. Then, you can delete the project.

- **Clusters must be named 'rec' in OLM-based deployments (RED-39825)** In OLM-deployed operators, the deployment of the cluster will fail if the name is not "rec". When the operator is deployed via the OLM, the security context constraints (scc) are bound to a specific service account name (namely, "rec"). The workaround is to name the cluster "rec".

- **Readiness probe incorrect on failures (RED-39300)** STS Readiness probe does not mark a node as "not ready" when running `rladmin status` on node failure.

- **Internal DNS and Kubernetes DNS may have conflicts (RED-37462)** DNS conflicts are possible between the cluster `mdns_server` and the K8s DNS. This only impacts DNS resolution from within cluster nodes for Kubernetes DNS names.

- **K8s-based 5.4.10 clusters seem to negatively affect existing 5.4.6 clusters (RED-37233)** Upgrade clusters to latest version.

- **Node CPU usage is reported instead of pod CPU usage (RED-36884)** In Kubernetes, the reported node CPU usage is the usage of the Kubernetes worker node hosting the REC pod.

- **An unreachable cluster has status running (RED-32805)** When a cluster is in an unreachable state, the state remains `running` instead of triggering an error.

- **Long cluster names cause routes to be rejected  (RED-25871)** A cluster name longer than 20 characters will result in a rejected route configuration because the host part of the domain name exceeds 63 characters. The workaround is to limit the cluster name to 20 characters or fewer.

- **Cluster CR (REC) errors are not reported after invalid updates (RED-25542)** A cluster CR specification error is not reported if two or more invalid CR resources are updated in sequence.


Redis Enterprise for Kubernetes 8.0.16-24 (March 2026) release notes

Summary: Feature release with OSS Cluster API support for external clients, ARM architecture support, and Redis Software 8.0.16-64.

Overview

Redis Enterprise for Kubernetes 8.0.16-24 is a maintenance release of [Redis Enterprise for Kubernetes 8.0.10]().

For version changes, supported distributions, and known limitations, see the [release notes for 8.0.10]().

Resolved issues

- Fixed an issue where an expired license caused the REC pod readiness probe to fail after restart <!--RED-185977-->
- Fixed a UBI9 dependency error that blocked operator image builds <!--RED-187506-->
- Added testing for OpenShift 4.21 <!--RED-190160-->
- Fixed Vault cache timeouts <!--RED-189494-->

Downloads

- **Redis Enterprise**: `redislabs/redis:8.0.16-64`
- **Operator**: `redislabs/operator:8.0.16-24`
- **Services Rigger**: `redislabs/k8s-controller:8.0.16-24`
- **Callhome client**: `redislabs/re-call-home-client:8.0.16-24`

Openshift downloads

- **OLM operator bundle**: `8.0.16-24.4`
- **Call Home Client**: `redislabs/call-home-client:8.0.16-24`