title: Overview

text:
The Redis Enterprise K8s 6.4.2-4 release supports Redis Enterprise Software 6.4.2 and contains new features and feature improvements.

The key features, bug fixes, and known limitations are described below.

title: Images

text:
* **Redis Enterprise**: `redislabs/redis:6.4.2-43`
* **Operator**: `redislabs/operator:6.4.2-4`
* **Services Rigger**: `redislabs/k8s-controller:6.4.2-4`

title: OpenShift images

text:
* **Redis Enterprise**: `registry.connect.redhat.com/redislabs/redis-enterprise:6.4.2-43.rhel8-openshift`
    (or `redislabs/redis-enterprise:6.4.2-43.rhel7-openshift` if upgrading from RHEL 7)
* **Operator**: `registry.connect.redhat.com/redislabs/redis-enterprise-operator:6.4.2-4`s
* **Services Rigger**: `registry.connect.redhat.com/redislabs/services-manager:6.4.2-4`

title: OpenShift OLM bundles

text: * Redis Enterprise operator bundle version: `v6.4.2-4.0`

title: New features

text:
* Cluster-level LDAP configuration support in REC (RED-83533)
* Public preview support for declarative Active-Active configuration (RED-86470)(RED-86470)

title: Feature improvements

text:
* New labeling method for multi-namespace REDB (RED-83102)
* Operator deployment uses built-in SCC in OpenShift (RED-90524)
* Support for Redis Enterprise 6.4.2-43
* Support added for K8s 1.26, EKS 1.24, AKS 1.25, Rancher 2.7/1.23-24
* Improved log collector display and error handling

title: Bug fixes

text:
* Deployment manifests referenced non-existent redis-enterprise-admission ServiceAccount (RED-90469)
* CVE-2022-1996 (RED-93026)
* CVE-2022-28948 (RED-93027)
* CVE-2021-44716 & CVE-2022-27664 (RED-93028)
* CVE-2018-20225

title: API changes

text:
The following fields were changed in the [Redis Enterprise cluster (REC) API]():

* Added `.spec.ldap` for configuring cluster-level LDAP settings
* Added `.spec.certificates.ldapClientCertificateSecretName` for configuring LDAP client certificate
* Added `.status.managedAPIs` to track APIs managed by the operator

* The following custom resources definitions were added:
  * `RedisEnterpriseRemoteCluster` (RERC)
  * `RedisEnterpriseActiveActiveDatabase` (REAADB)

title: Compatibility notes

title: Deprecated features

text:
* Support for Gesher, the advanced admission control configuration, is deprecated.
* The `app.redislabs.com/v1alpha1` API version of the RedisEnterpriseCluster (REC) custom resource is deprecated and will be removed in a subsequent release. Customers should switch to use the `app.redislabs.com/v1` API version instead.

title: Supported distributions

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

| **Kubernetes version**  | 1.21       | 1.22       | 1.23       | 1.24       | 1.25       | 1.26       |
|:------------------------|:----------:|:----------:|:----------:|:----------:|:----------:|:----------:|
| Community Kubernetes    |            | deprecated | supported  | supported  | supported  | supported* |
| Amazon EKS              |            | supported  | supported  | supported* |            |            |
| Azure AKS               |            |            | deprecated | supported  | supported* |            |
| Google GKE              |            | supported  | supported  | supported  | supported  |            |
| Rancher 2.6             | deprecated | supported  | supported  | supported  |            |            |
| Rancher 2.7             |            |            | supported* | supported* |            |            |
| VMware TKG 1.6          |            | supported  | supported  |            |            |            |
| **OpenShift version**   | **4.8**    | **4.9**    | **4.10**   | **4.11**   |  **4.12**  |            |
|                         | deprecated | deprecated | supported  | supported  | supported* |            |
| **VMware TKGI version** | **1.12**   | **1.13**   | **1.14**   | **1.15**   |            |            |
|                         |            | deprecated | supported  | supported  |            |            |

\* Support added in this release

title: Before upgrading

text:
Be aware the following changes included in this release affect the upgrade process. Please read carefully before upgrading.

* **Supported upgrade paths**

  If you are using a version earlier than 6.2.10-45, you cannot upgrade directly to this release. You must upgrade to 6.2.10-45 before you can upgrade to versions 6.2.18 or later.

* **ValidatingWebhookConfiguration**

  This release uses 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.

title: Active-Active preview known limitations

text:
* No support for Hashicorp Vault for storing secrets (RED-95805)
* No module support (RED-95153)
* No support for client certificates in secrets (RED-95724)
* No support for backup configuration (RED-95724)
* No support for upgrading the database Redis version
* REAADB secret status isn't updated in source cluster (RED-96296)

  The workaround is to view the secret status in one of the remote clusters.
* Invalid REAADB is not rejected by admission might get deleted after apply. (RED-96300)

  Fix the problems with the REAADB and reapply. Contact support if you aren't sure why the REAADB is invalid.
* Admission is not blocking REAADB with `shardCount` which exceeds license quota. (RED-96301)

  Fix the problems with the REAADB and reapply.
* RERC resources must have a unique name (`<rec-name>/<rec-namespace>`). (RED-96302)

* Only global database options are supported, not support for specifying configuration per location.
* Can't automatically update the cluster secret via the operator (can be updated manually).
* No support for migration from old (manual) Active-Active database method to new Active-Active controller.

title: Known limitations

text:
* REC creation might fail using form view on OpenShift. (RED-100517)

  To avoid this, use the YAML view. This will be fixed in the next release.

title: Large clusters

text:
On clusters with more than 9 REC nodes, a Kubernetes upgrade can render the Redis cluster unresponsive in some cases. A fix is available in the 6.4.2-5 release. Upgrade your operator version to 6.4.2-5 or later before upgrading your Kubernetes cluster. (RED-93025)

* Resharding fails for rack-aware databases with no replication (RED-97971)

  When a database is configured as [rack-aware]() and replication is turned off, the resharding operation fails.

  Workaround:
    Before resharding your database, [turn off rack awareness](). Set the `spec.rackAware` field in your REDB custom resource to `false`.
    After the resharding process is complete, you can [re-enable rack awareness]().

* 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.
* An unreachable cluster has status running (RED-32805)

  When a cluster is in unreachable state, the state remains `running` instead of triggering an error.
* 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.
* 5.4.10 negatively impacts 5.4.6 (RED-37233)

  Kubernetes-based 5.4.10 deployments seem to negatively impact existing 5.4.6 deployments that share a Kubernetes cluster.
* 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.
* 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".
* REC clusters fail to start on Kubernetes clusters with unsynchronized clocks (RED-47254)

  When REC clusters are deployed on Kubernetes clusters with unsynchronized 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.
* Hashicorp Vault integration - no support for Gesher (RED-55080)

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

  There is no workaround at this time except to ignore the errors.
* PVC size issues when using decimal value in spec (RED-62132)

  The workaround for this issue is to make sure you use integer values for the PVC size.
* 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 the [quick start]().
* `autoUpgrade` set to `true` can cause unexpected bdb upgrades when `redisUpgradePolicy` is set to `true` (RED-72351)

  Contact support if your deployment is impacted.

  ## Security

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


title: Redis Enterprise for Kubernetes 7.2.4-12 (Dec 2023) release notes

summary: This is a maintenance release with a few enhancements/fixes on the Kubernetes product and a new Redis Enterprise container version.

page_type: content

title: Highlights

role: overview

text: This is a maintenance release with a few enhancements/fixes on the Kubernetes product and a newer Redis Enterprise container version.

title: New in this release

role: content

title: Enhancements

text:
- Added to [supported distributions](#supported-distributions)
- Added support for Redis Enterprise Software 7.2.4-92 (RED-113750)
- Replaced usage of config maps for readiness check and prestop scripts of Redis Enterprise pods (RED-81443)

title: Resolved issues

text:
- Fixed issues around REC creation when namespace contains old resources from previous installation (RED-100669) (RED-100668)
- Fixed constant updates to watched namespaces REDB services (RED-103264)
- Fixed labeling of old operator configmaps (RED-105517)
- Removed automatic upgrades of modules during upgrades (RED-106834)
- Fixed unexpected restart of container during cluster recovery (RED-108511)
- Fixed timeout of prestop (RED-111471)
- Fixed deployment issues on TKG (RED-111271)

title: Version changes

role: compatibility

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

title: Breaking changes

text:
The following changes included in this release affect the upgrade process. Please read carefully before upgrading to 7.2.4-12.

#### 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 has been added to replace the hard-coded timeout of 15 minutes for a node to be stopped/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.

title: Upcoming changes

text: - A future release of Redis Enterprise will remove support for RHEL7. We recommend migrating to RHEL8.

title: Supported distributions

text:
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.

⚠ 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.23** | **1.24** | **1.25** | **1.26** | **1.27** | **1.28** |
|---|---|---|---|---|---|---|
| Community Kubernetes |  | ✅ | ✅ | ✅ | ✅ | ✅ |
| Amazon EKS | ⚠ | ✅ | ✅ | ✅ | ✅ |  |
| Azure AKS |  |  | ✅ | ✅ | ✅ |  |
| Google GKE | ❌ | ✅ | ✅ | ✅ | ✅ |  |
| Rancher 2.6 | ❌ | ❌ |  |  |  |  |
| Rancher RKE2 | ⚠ | ✅ | ✅ | ✅ |  |  |
| VMware TKG 2.1 | ⚠ | ✅ |  |  |  |  |
| VMware TKG 2.2 | ✅ | ✅ | ✅ |  |  |  |
| VMware TKG 2.3 |  | ✅ | ✅ | ✅ |  |  |
| **OpenShift version** | **4.10** | **4.11** | **4.12** | **4.13** | **4.14** |  |
|  | ❌ | ✅ | ✅ | ✅ | ✅ |  |
| **VMware TKGI version** | **1.14** | **1.15** |  |  |  |  |
|  | ❌ | ✅ |  |  |  |  |

title: Downloads

text:
- **Redis Enterprise**: `redislabs/redis:7.2.4-92`
- **Operator**: `redislabs/operator:7.2.4-12`
- **Services Rigger**: `redislabs/k8s-controller:7.2.4-12.`

#### OpenShift images

- **Redis Enterprise**: `registry.connect.redhat.com/redislabs/redis-enterprise:7.2.4-92.rhel8-openshift`
    (or `redislabs/redis-enterprise:7.2.4-92.rhel7-openshift` if upgrading from RHEL 7)
- **Operator**: `registry.connect.redhat.com/redislabs/redis-enterprise-operator:7.2.4-12`
- **Services Rigger**: `registry.connect.redhat.com/redislabs/services-manager:7.2.4-12`

#### OLM bundle

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

title: Known limitations

text: 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.2.4 release notes]().

title: Existing limitations

text:
- **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.


title: Redis Enterprise for Kubernetes 7.2.4-12 (March 2024) release notes

summary: This is a maintenance release to support Redis Enterprise Software version 7.2.4-105.

title: Highlights

title: New in this release

title: Enhancements

text: - Added support for Redis Enterprise Software 7.2.4-105 (RED-113750)

title: Version changes

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

title: Breaking changes

title: Upcoming changes

title: Supported distributions

title: Downloads

text:
- **Redis Enterprise**: `redislabs/redis:7.2.4-105`
- **Operator**: `redislabs/operator:7.2.4-12`
- **Services Rigger**: `redislabs/k8s-controller:7.2.4-12.`

#### OpenShift images

- **Redis Enterprise**: `registry.connect.redhat.com/redislabs/redis-enterprise:7.2.4-105.rhel8-openshift`
    (or `redislabs/redis-enterprise:7.2.4-105.rhel7-openshift` if upgrading from RHEL 7)
- **Operator**: `registry.connect.redhat.com/redislabs/redis-enterprise-operator:7.2.4-12`
- **Services Rigger**: `registry.connect.redhat.com/redislabs/services-manager:7.2.4-12`

#### OLM bundle

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

title: Known limitations

title: Existing limitations


title: Redis Enterprise for Kubernetes 7.2.4-12 (August 2024) release notes

summary: This is a maintenance release to support Redis Enterprise Software version 7.2.4-109.

title: Highlights

title: New in this release

title: Enhancements

text: - Added support for Redis Enterprise Software 7.2.4-109.

title: Version changes

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

title: Breaking changes

text:
The following changes included in this release affect the upgrade process. Please read carefully before upgrading to 7.2.4-12.

#### 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 has been added to replace the hard-coded timeout of 15 minutes for a node to be stopped/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.

title: Upcoming changes

title: Supported distributions

title: Downloads

text:
- **Redis Enterprise**: `redislabs/redis:7.2.4-109`
- **Operator**: `redislabs/operator:7.2.4-12`
- **Services Rigger**: `redislabs/k8s-controller:7.2.4-12.`

#### OpenShift images

- **Redis Enterprise**: `registry.connect.redhat.com/redislabs/redis-enterprise:7.2.4-109.rhel8-openshift`
    (or `redislabs/redis-enterprise:7.2.4-109.rhel7-openshift` if upgrading from RHEL 7)
- **Operator**: `registry.connect.redhat.com/redislabs/redis-enterprise-operator:7.2.4-12`
- **Services Rigger**: `registry.connect.redhat.com/redislabs/services-manager:7.2.4-12`

#### OLM bundle

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

title: Known limitations

title: Existing limitations

text:
- **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 the 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.


title: Redis Enterprise for Kubernetes 7.2.4-12 (October 2024) release notes

summary: This is a maintenance release to support Redis Enterprise Software version 7.2.4-117.

title: Highlights

title: New in this release

title: Enhancements

text: - Added support for Redis Enterprise Software 7.2.4-117.

title: Version changes

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

title: Breaking changes

title: Upcoming changes

title: Supported distributions

title: Downloads

text:
- **Redis Enterprise**: `redislabs/redis:7.2.4-117`
- **Operator**: `redislabs/operator:7.2.4-12`
- **Services Rigger**: `redislabs/k8s-controller:7.2.4-12.`

#### OpenShift images

- **Redis Enterprise**: `registry.connect.redhat.com/redislabs/redis-enterprise:7.2.4-117.rhel8-openshift`
    (or `redislabs/redis-enterprise:7.2.4-117.rhel7-openshift` if upgrading from RHEL 7)
- **Operator**: `registry.connect.redhat.com/redislabs/redis-enterprise-operator:7.2.4-12`
- **Services Rigger**: `registry.connect.redhat.com/redislabs/services-manager:7.2.4-12`

#### OLM bundle

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

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

title: Known limitations

title: Existing limitations


title: Redis Enterprise for Kubernetes 7.2.4-12 (January 2025) release notes

title: Highlights

text: This is a maintenance release to support Redis Enterprise Software version 7.2.4-118. For information on supported distributions, breaking changes, and limitations, see the previous (7.2.4-12 release notes).

title: Downloads

text:
- **Redis Enterprise**: `redislabs/redis:7.2.4-118`
- **Operator**: `redislabs/operator:7.2.4-12`
- **Services Rigger**: `redislabs/k8s-controller:7.2.4-12.`

#### OpenShift images

- **Redis Enterprise**: `registry.connect.redhat.com/redislabs/redis-enterprise:7.2.4-118.rhel8-openshift`
    (or `redislabs/redis-enterprise:7.2.4-118.rhel7-openshift` if upgrading from RHEL 7)
- **Operator**: `registry.connect.redhat.com/redislabs/redis-enterprise-operator:7.2.4-12`
- **Services Rigger**: `registry.connect.redhat.com/redislabs/services-manager:7.2.4-12`

#### OLM bundle

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

title: Security

role: security

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


title: Redis Enterprise for Kubernetes 7.2.4-12 (June 2025) release notes

title: Highlights

text: This is a maintenance release to support Redis Enterprise Software version 7.2.4-130. For information on supported distributions, breaking changes, and limitations, see the previous [7.2.4-12 release notes]().

title: Downloads

text:
- **Redis Enterprise**: `redislabs/redis:7.2.4-130`
- **Operator**: `redislabs/operator:7.2.4-12`
- **Services Rigger**: `redislabs/k8s-controller:7.2.4-12.`

title: OpenShift images

text:
- **Redis Enterprise**: `registry.connect.redhat.com/redislabs/redis-enterprise:7.2.4-130.rhel8-openshift`
    (or `redislabs/redis-enterprise:7.2.4-130.rhel7-openshift` if upgrading from RHEL 7)
- **Operator**: `registry.connect.redhat.com/redislabs/redis-enterprise-operator:7.2.4-12`
- **Services Rigger**: `registry.connect.redhat.com/redislabs/services-manager:7.2.4-12`

title: OLM bundle

text: **Redis Enterprise operator bundle** : `v7.2.4-12.39`

title: Security

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


title: Redis Enterprise for Kubernetes 7.2.4-12 (March 2025) release notes

summary: This is a maintenance release to support Redis Enterprise Software version 7.2.4-118.

title: Highlights

text: This is a maintenance release to support Redis Enterprise Software version 7.2.4-122. For information on supported distributions, breaking changes, and limitations, see the previous [7.2.4-12 release notes]().

title: Downloads

text:
- **Redis Enterprise**: `redislabs/redis:7.2.4-122`
- **Operator**: `redislabs/operator:7.2.4-12`
- **Services Rigger**: `redislabs/k8s-controller:7.2.4-12.`

title: OpenShift images

text:
- **Redis Enterprise**: `registry.connect.redhat.com/redislabs/redis-enterprise:7.2.4-122.rhel8-openshift`
    (or `redislabs/redis-enterprise:7.2.4-118.rhel7-openshift` if upgrading from RHEL 7)
- **Operator**: `registry.connect.redhat.com/redislabs/redis-enterprise-operator:7.2.4-12`
- **Services Rigger**: `registry.connect.redhat.com/redislabs/services-manager:7.2.4-12`

title: OLM bundle

text: **Redis Enterprise operator bundle** : `v7.2.4-12.35`

title: Security

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


title: Redis Enterprise for Kubernetes 7.2.4-15 (October 2025) release notes

title: Highlights

text: This is a maintenance release to support Redis Enterprise Software version 7.2.4-144. For information on supported distributions, breaking changes, and limitations, see the previous [7.2.4-15 release notes]().

title: Downloads

text:
- **Redis Enterprise**: `redislabs/redis:7.2.4-144`
- **Operator**: `redislabs/operator:7.2.4-15`
- **Services Rigger**: `redislabs/k8s-controller:7.2.4-15`

title: OpenShift images

text:
- **Redis Enterprise**: `registry.connect.redhat.com/redislabs/redis-enterprise:7.2.4-144.rhel8-openshift`
- **Operator**: `registry.connect.redhat.com/redislabs/redis-enterprise-operator:7.2.4-15`
- **Services Rigger**: `registry.connect.redhat.com/redislabs/services-manager:7.2.4-15`

title: OLM bundle

text: **Redis Enterprise operator bundle** : `v7.2.4-15.41`

title: Security

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


title: Redis Enterprise for Kubernetes 7.2.4-15 (September 2025) release notes

summary: This is a maintenance release to support Redis Enterprise Software version 7.2.4-138. RHEL7 support has been removed.

title: Highlights

text: This is a maintenance release to support Redis Enterprise Software version 7.2.4-138. For information on supported distributions, breaking changes, and limitations, see the previous [7.2.4-12 release notes]().

title: Breaking changes

text: **RHEL7 support removed**: Redis Enterprise Software 7.2.4-138 removes support for RHEL7. RHEL7-based OpenShift images are no longer available. Migrate to RHEL8-based images before upgrading.

title: Downloads

text:
- **Redis Enterprise**: `redislabs/redis:7.2.4-138`
- **Operator**: `redislabs/operator:7.2.4-15`
- **Services Rigger**: `redislabs/k8s-controller:7.2.4-15`

title: OpenShift images

text:
- **Redis Enterprise**: `registry.connect.redhat.com/redislabs/redis-enterprise:7.2.4-138.rhel8-openshift`
- **Operator**: `registry.connect.redhat.com/redislabs/redis-enterprise-operator:7.2.4-15`
- **Services Rigger**: `registry.connect.redhat.com/redislabs/services-manager:7.2.4-15`

title: OLM bundle

text: **Redis Enterprise operator bundle** : `v7.2.4-15.1`

title: Security

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


title: Redis Enterprise for Kubernetes 7.2.4-16 (February 2026) release notes

title: Highlights

text: This is a maintenance release to support Redis Enterprise Software version 7.2.4-153. For information on supported distributions, breaking changes, and limitations, see the previous [7.2.4-15 release notes]().

title: Downloads

text:
- **Redis Enterprise**: `redislabs/redis:7.2.4-153`
- **Operator**: `redislabs/operator:7.2.4-16`
- **Services Rigger**: `redislabs/k8s-controller:7.2.4-16`

title: OpenShift images

text:
- **Redis Enterprise**: `registry.connect.redhat.com/redislabs/redis-enterprise:7.2.4-153.rhel8-openshift`
- **Operator**: `registry.connect.redhat.com/redislabs/redis-enterprise-operator:7.2.4-16`
- **Services Rigger**: `registry.connect.redhat.com/redislabs/services-manager:7.2.4-16`

title: OLM bundle

text: **Redis Enterprise operator bundle** : `v7.2.4-16.2`

title: Security


title: Redis Enterprise for Kubernetes release notes 7.2.4-2 (Aug 2023)

summary: The primary purpose this release is supporting Redis Enterprise 7.2.4.

title: Highlights

text:
The primary purpose this release is supporting [Redis Enterprise 7.2.4](), which is a major Redis Enterprise Software update. As such, we reduced the scope of changes to support the underlying change of RS 7.2 and a few significant fixes.

The following are the notable changes:

- Support for [Redis Enterprise 7.2.4]()

    - New major version of Redis, 7.2
    - [Changes to modules and cluster recovery]()

Redis Enterprise Software 7.2.4-52 includes several issues that also effect Redis Enterprise for Kubernetes and are not listed below. Review the Redis Enterprise Software 7.2.4 [breaking changes]() and [known limitations.]()

- New default engine, Speedb, for Auto Tiering (formerly Redis on Flash)

- Changes to [supported Kubernetes distributions]()

title: New in this release

title: Enhancements

text:
- Support for [Redis Enterprise 7.2.4]() (RED-73681)
- New default engine, Speedb, for Auto Tiering (formerly Redis on Flash) (RED-90850)
- Security context hardening (RED-98447)

title: Resolved issues

text:
- Fixed: Services or routes from the Active-Active setup might not be removed (RED-77752)
- Fixed: Admission controller may not alert when patching the REAADB with missing secret or RERC (RED-104463)

title: API changes

text:
The following fields were added to the RedisEnterpriseCluster (REC) custom resource definition (CRD):

- Added `status.BundledDatabaseRedisVersions.major` as a Boolean field indicating whether the Redis version is major.
- Added `spec.RedisOnFlashSpec.bigStoreDriver` to indicate the storage engine used for Auto Tiering (formerly Redis on Flash).

title: Version changes

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

title: Breaking changes

text:
The following changes included in this release affect the upgrade process. Please read carefully before upgrading to 7.2.4-2.

#### 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.

title: Deprecations

text:
- Gesher (advanced admission control configuration support) previously deprecated, is no longer supported.
- Deprecated `spec.RedisOnFlashSpec.flashStorageEngine` field for the RedisEnterpriseCluster. Use `bigStoreDriver` field to indicate storage engines going forward.

title: Supported distributions

text:
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.

⚠ 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.22** | **1.23** | **1.24** | **1.25** | **1.26** | **1.27** |
|---|---|---|---|---|---|---|
| Community Kubernetes | ❌ | ❌ | ✅ | ✅ | ✅ | ✅ |
| Amazon EKS | ❌ | ⚠ | ✅ | ✅ | ✅ | ✅ |
| Azure AKS |  | ❌ | ❌ | ✅ | ✅ | ✅ |
| Google GKE | ❌ | ⚠ | ✅ | ✅ | ✅ | ✅ |
| Rancher 2.6 | ❌ | ❌ | ⚠ |  |  |  |
| Rancher 2.7 |  | ⚠ | ✅ | ✅ |  |  |
| VMware TKG 1.6 | ⚠ | ⚠ |  |  |  |  |
| **OpenShift version** | **4.9** | **4.10** | **4.11** | **4.12** | **4.13** |  |
|  | ❌ | ⚠ | ✅ | ✅ | ✅ |  |
| **VMware TKGI version** | **1.13** | **1.14** | **1.15** | **1.16** |  |  |
|  | ❌ | ⚠ | ✅ | ✅ |  |  |

title: Downloads

text:
- **Redis Enterprise**: `redislabs/redis:7.2.4-52`
- **Operator**: `redislabs/operator:7.2.4-2`
- **Services Rigger**: `redislabs/k8s-controller:7.2.4-2.`

#### OpenShift images

- **Redis Enterprise**: `registry.connect.redhat.com/redislabs/redis-enterprise:7.2.4-52.rhel8-openshift`
    (or `redislabs/redis-enterprise:7.2.4-52.rhel7-openshift` if upgrading from RHEL 7)
- **Operator**: `registry.connect.redhat.com/redislabs/redis-enterprise-operator:7.2.4-2`
- **Services Rigger**: `registry.connect.redhat.com/redislabs/services-manager:7.2.4-2`

#### OLM bundle

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

It is not possible to upgrade your OLM deployment to version 7.2.4 from version 6.2.4-8 (November release). Uninstall 6.2.4-8 and perform a fresh install of 7.2.4.

title: Known limitations

text: 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.2.4 release notes]().

title: New limitations

text:
- **REDBs created with versions before 6.2.10-4 will automatically upgrade modules when the cluster is upgraded (RED-106834)**

- **Cannot upgrade or recover clusters if there are databases with manually uploaded modules (RED-107711 RED-106872)** Contact support.

In version 7.2.4, old module versions and manually uploaded modules are not persisted. If databases are not upgraded after cluster upgrade, and require cluster recovery afterwards, you'll need to contact Redis support. This issue will be fixed in the next maintenance release by moving the stored location of the modules.

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

title: Existing limitations

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

- **Misleading error appears when a service creation has failed due to service already existing "`provided IP is already allocated`" (RED-100669)** Delete the service manually.

- **Existing OpenShift route during REC creation might prevent REC from starting (RED-100668)** Delete the route manually.

- **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.


title: Redis Enterprise for Kubernetes release notes 7.2.4-7 (Oct 2023)

summary: This is a minor maintenance release with a few enhancements/fixes on the Kubernetes product, and a newer Redis Enterprise container version.

title: Highlights

text:
This is a minor maintenance release with a few enhancement/fixes on the Kubernetes product, and a newer Redis Enterprise container version.

The following are the notable changes:
- Customers who are on RHEL 7 based images and who are already using this version of 7.2 can migrate to RHEL 8 based images when they upgrade.
    - Previously, you could not migrate a cluster to newer OS version.
    - All customers should plan to move to RHEL 8 based images. The next major version of Redis Enterprise will not support RHEL 7.
    - This process requires specific pre-requisites and actions. Updated guides are being developed and will be available soon.
- Added VMware TKG 2.1 and 2.2 to the [Supported distributions](#supported-distributions) table.

title: New in this release

title: Enhancements

text:
- Support for migration from RHEL7 images to RHEL8 during upgrade (RED-106785)
- Support for Redis Enterprise Software version 7.2.4-64 (RED-108832)

title: Resolved issues

text: - Fixed cluster recovery flow when non default modules are used (RED-107711 RED-106872)

title: Version changes

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

title: Breaking changes

text:
The following changes included in this release affect the upgrade process. Please read carefully before upgrading to 7.2.4-7.

#### 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.

title: Upcoming changes

text: - A future release of Redis Enterprise will remove support for RHEL7. We recommend migrating to RHEL8.

title: Supported distributions

text:
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.

⚠ 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.22** | **1.23** | **1.24** | **1.25** | **1.26** | **1.27** |
|---|---|---|---|---|---|---|
| Community Kubernetes | ❌ | ❌ | ✅ | ✅ | ✅ | ✅ |
| Amazon EKS | ❌ | ⚠ | ✅ | ✅ | ✅ | ✅ |
| Azure AKS |  | ❌ | ❌ | ✅ | ✅ | ✅ |
| Google GKE | ❌ | ⚠ | ✅ | ✅ | ✅ | ✅ |
| Rancher 2.6 | ❌ | ❌ | ⚠ |  |  |  |
| Rancher 2.7 |  | ⚠ | ✅ | ✅ |  |  |
| VMware TKG 1.6 | ⚠ | ⚠ |  |  |  |  |
| VMware TKG 2.1 | ⚠ | ⚠ | ✅ |  |  |  |
| VMware TKG 2.2 |  | ✅ | ✅ | ✅ |  |  |
| **OpenShift version** | **4.9** | **4.10** | **4.11** | **4.12** | **4.13** |  |
|  | ❌ | ⚠ | ✅ | ✅ | ✅ |  |
| **VMware TKGI version** | **1.13** | **1.14** | **1.15** | **1.16** |  |  |
|  | ❌ | ⚠ | ✅ | ✅ |  |  |

title: Downloads

text:
- **Redis Enterprise**: `redislabs/redis:7.2.4-64`
- **Operator**: `redislabs/operator:7.2.4-7`
- **Services Rigger**: `redislabs/k8s-controller:7.2.4-7.`

#### OpenShift images

- **Redis Enterprise**: `registry.connect.redhat.com/redislabs/redis-enterprise:7.2.4-64.rhel8-openshift`
    (or `redislabs/redis-enterprise:7.2.4-64.rhel7-openshift` if upgrading from RHEL 7)
- **Operator**: `registry.connect.redhat.com/redislabs/redis-enterprise-operator:7.2.4-7`
- **Services Rigger**: `registry.connect.redhat.com/redislabs/services-manager:7.2.4-7`

#### OLM bundle

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

It is not possible to upgrade your OLM deployment to version 7.2.4 from version 6.2.4-8 (November release). Uninstall 6.2.4-8 and perform a fresh install of 7.2.4.

title: Known limitations

title: Existing limitations

text:
- **REDBs created with versions before 6.2.10-4 will automatically upgrade modules when the cluster is upgraded (RED-106834)**

- **When modifying the database suffix for an Active-Active database, while the service-rigger is in a terminating state, the services-rigger will detele 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.

- **Misleading error appears when a service creation has failed due to service already existing "`provided IP is already allocated`" (RED-100669)** Delete the service manually.

- **Existing OpenShift route during REC creation might prevent REC from starting (RED-100668)** Delete the route manually.

- **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.


title: 7.2.4 release notes

summary: Support for Redis Enterprise 7.2.4, platform support updates, and bug fixes.

summary: This is a maintenance release to support Redis Enterprise Software version 7.2.4-153.

summary: This is a maintenance release to support Redis Enterprise Software version 7.2.4-144.

summary: This is a maintenance release to support Redis Enterprise Software version 7.2.4-130.

title: Highlights

text:
The primary purpose this release is supporting [Redis Enterprise 7.2.4](), which is a major Redis Enterprise Software update. As such, we reduced the scope of changes to support the underlying change of RS 7.2 and a few significant fixes.

The following are the notable changes:

- Support for [Redis Enterprise 7.2.4]()

    - New major version of Redis, 7.2
    - [Changes to modules and cluster recovery]()

Redis Enterprise Software 7.2.4-52 includes several issues that also effect Redis Enterprise for Kubernetes and are not listed below. Review the Redis Enterprise Software 7.2.4 [breaking changes]() and [known limitations.]()

title: Detailed release notes

title: Version changes

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

title: Breaking changes

title: Deprecations

title: Supported distributions

title: Known limitations

text:
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.2.4 release notes]().

Pay particular attention to the [cluster recovery limitation]() if you use manually uploaded modules.

- **Cannot upgrade or recover clusters if there are databases with manually uploaded modules (RED-107711 RED-106872)** Contact support.

- **REDBs created with versions before 6.2.10-4 will automatically upgrade modules when the cluster is upgraded (RED-106834)**

- **When modifying the database suffix for an Active-Active database, while the service-rigger is in a terminating state, the services-rigger will detele 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.

- **Misleading error appears when a service creation has failed due to service already existing "`provided IP is already allocated`" (RED-100669)** Delete the service manually.

- **Existing OpenShift route during REC creation might prevent REC from starting (RED-100668)** Delete the route manually.

- **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.


title: Redis Enterprise for Kubernetes 7.22.0-11 (June 2025) release notes

summary: This is a maintenance release to support Redis Enterprise Software version 7.22.0-95.

title: Highlights

text: This is a maintenance release to support [Redis Enterprise Software version 7.22.0-95](). For version changes, supported distributions, and known limitations, see the [release notes for 7.22.0-7 (April 2025)]().

title: Downloads

text:
- **Redis Enterprise**: `redislabs/redis:7.22.0-95`
- **Operator**: `redislabs/operator:7.22.0-11`
- **Services Rigger**: `redislabs/k8s-controller:7.22.0-11`
- **Call Home Client**: `redislabs/re-call-home-client:7.22.0-11`

title: Openshift downloads

text:
- **OLM operator bundle**: `v7.22.0-11.2`
- **Call Home Client**: `redislabs/call-home-client:7.22.0-11`


title: Redis Enterprise for Kubernetes 7.22.0-15 (July 2025) release notes

summary: Feature release with Helm chart general availability, Kubernetes 1.33 and OpenShift 4.19 support, Redis Software 7.22.0-216 support, and enhancements.

title: Highlights

text: * Helm chart support is now generally available.

title: New in this release

text: Redis Enterprise for Kubernetes 7.22.0-15 is a feature release that includes enhancements, platform updates, and support for Redis Software 7.22.0-216.

title: Enhancements

text:
* Call home - support HTTP proxy configuration (RED-156935)
* Helm - optimize installation time (RED-153889)
* Add support for migrating to a Helm-based installation from a non-Helm installation (RED-113099)
* Support upgrade using Helm (RED-153890)
* Support any custom port for database service (different from cluster database port) (RED-156946)
* Hardened the securityContext of init containers created when readOnlyRootFilesystem is enabled
* Kubernetes platform updates, support for Kubernetes 1.33
* Support for Redis Software 7.22.0-216 (RED-163025)

title: Resolved Issues

text:
* Adding `servicesAnnotations` in the REC spec keeps updating the services in a loop (RED-154777, RED-158816)
* New call home job is not created if the old one is stuck due to pod in `imagePullBackoff` (RED-157526)
* REAADB ACL roles do not get properly assigned according to `rolesPermissions` in spec (RED-158955)
* CVE fixes
* `allowPrivilegeEscalation` is unset in the init container for `readOnlyRootFilesystem` (RED-163637)

title: API changes

text:
| CRD | Field | Change | Description |
| ----- | :---- | :---- | :---- |
| REAADB | `spec.databaseServicePort` | Add | A custom port to be exposed by the database services. Can be modified/added/removed after REDB creation. If set, it replaces the default service port (namely, `databasePort` or `defaultRedisPort`). |
| REC | `spec.usageMeterSpec.CallHomeClient.proxySecretName` | Add | If needed, add proxy details in secret. The name of the proxy secret in the secret, can send the following keys: `proxy-url`, `proxy-username`, `proxy-password` (the URL includes the proxy port). |
| REDB | `spec.databaseServicePort` | Add | A custom port to be exposed by the database services. Can be modified/added/removed after REDB creation. If set, it replaces the default service port (namely, `databasePort` or `defaultRedisPort`). |

title: RHEL9-based image

text:
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]()

title: Supported distributions

text:
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 Kubernetes.

:warning: Deprecated – This distribution is still supported for this version of Redis Enterprise 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.28** | **1.29** | **1.30** | **1.31** | **1.32** | **1.33** |
|---|---|---|---|---|---|---|
| **Community K8s** |  |  | :warning: | ✅ | ✅ | ✅ |
| **Amazon EKS** |  |  | :warning: | ✅ | ✅ | ✅ |
| **Azure AKS** |  |  | :warning: | ✅ | ✅ | ✅ |
| **Google GKE** |  |  | :warning: | ✅ | ✅ | ✅ |
| **Rancher** | :warning: | ✅ | ✅ |  |  |  |
| **OpenShift** | **4.15** | **4.16** | **4.17** | **4.18** | **4.19** |  |
|  | :warning: | ✅ | ✅ | ✅ | ✅ |  |
| **VMware TKGI** | **1.19** | **1.20** | **1.21** |  |  |  |
|  | :warning: | ✅ | ✅ |  |  |  |

title: Downloads

text:
- **Redis Enterprise**: `redislabs/redis:7.22.0-216`
- **Operator**: `redislabs/operator:7.22.0-15`
- **Services Rigger**: `redislabs/k8s-controller:7.22.0-15`
- **Call Home Client**: `redislabs/re-call-home-client:7.22.0-15`

title: Openshift downloads

text:
- **OLM operator bundle**: `7.22.0-15.0`
- **Call Home Client**: `redislabs/call-home-client:7.22.0-15`

title: Known limitations

text: See [7.22.0 releases]() for information on known limitations.


title: Redis Enterprise for Kubernetes 7.22.0-16 (August 2025) release notes

summary: This is a maintenance release to support Redis Enterprise Software version 7.22.0-241.

title: Highlights

text: This is a maintenance release to support [Redis Enterprise Software version 7.22.0-241](). For version changes, supported distributions, and known limitations, see the [release notes for 7.22.0-15 (July 2025)]().

title: Downloads

text:
- **Redis Enterprise**: `redislabs/redis:7.22.0-241`
- **Operator**: `redislabs/operator:7.22.0-16`
- **Services Rigger**: `redislabs/k8s-controller:7.22.0-16`
- **Call Home Client**: `redislabs/re-call-home-client:7.22.0-16`

title: Openshift downloads

text:
- **OLM operator bundle**: `v7.22.0-16.0`
- **Call Home Client**: `redislabs/call-home-client:7.22.0-16`

title: Known limitations


title: Redis Enterprise for Kubernetes 7.22.0-17 (September 2025) release notes

summary: This is a maintenance release to support Redis Enterprise Software version 7.22.0-250.

title: Highlights

text: This is a maintenance release to support [Redis Enterprise Software version 7.22.0-250](). For version changes, supported distributions, and known limitations, see the [release notes for 7.22.0-15 (July 2025)]().

title: Downloads

text:
- **Redis Enterprise**: `redislabs/redis:7.22.0-250`
- **Operator**: `redislabs/operator:7.22.0-17`
- **Services Rigger**: `redislabs/k8s-controller:7.22.0-17`
- **Call Home Client**: `redislabs/re-call-home-client:7.22.0-17`

title: Openshift downloads

text:
- **OLM operator bundle**: `v7.22.0-17.0`
- **Call Home Client**: `redislabs/call-home-client:7.22.0-17`

title: Known limitations


title: Redis Enterprise for Kubernetes 7.22.0-7 (April 2025) release notes

summary: Feature release with Redis Software 7.22.0-28 support, enhancements, and platform updates.

title: New in the release

text: Redis Enterprise for Kubernetes 7.22.0-7 is a feature release that includes enhancements, platform updates, and support for Redis Software 7.22.0-28.

title: Enhancements

text:
- Added support for Redis Software 7.22.0.
- Enabled support for Active-Active databases (REAADB) in multi-namespace deployments.
- Defaulted new installations and upgrades to unprivileged mode, which uses a more secure security context without additional Linux capabilities.
- A new cronjob is created by the operator using the `redislabs/re-call-home-client:7.22.0-7` image.
- Updated supported Kubernetes platforms.

title: API changes

text:
| **CRD** | **Field** | **Change** | **Description** |
|--------|-----------|------------|-----------------|
| REAADB | `spec.participatingClusters[].namespace` | Added | Specifies the namespace in which the REAADB object will be deployed in the corresponding participating cluster. Make sure that the Redis Enterprise operator is configured to watch this namespace and that the required RBAC configuration is in place. For more information, see [Multi-namespace deployments](). If no namespace is specified, the REAADB object is deployed to the REC’s namespace in the corresponding cluster. |
| REC | `spec.usageMeter.callHomeClient` | Added | Configuration for the call home client. For details, see the [REC API reference](). |
| REC | `spec.securityContext.resourceLimits` | Added | Configuration that allows Redis Enterprise to adjust system resource settings. For details, see the [REC API reference](). |

title: Breaking changes

text: By default, the operator no longer sets additional Linux capabilities in the security context. If your deployment requires capabilities such as `SYS_RESOURCE`, see [Allow automatic resource adjustment]().

title: RHEL9-based image

title: Supported distributions

text:
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 Kubernetes.

:warning: Deprecated – This distribution is still supported for this version of Redis Enterprise 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** |  |  |  | ❌ | ✅ | ✅ | ✅ |
| **Azure AKS** |  |  |  | ❌ | ✅ | ✅ | ✅ |
| **Google GKE** |  |  |  | ❌ | ✅ | ✅ | ✅ |
| **Rancher** |  | ❌ | ✅ | ✅ | ✅ |  |  |
| **VMware TKG 2.4** | :warning: | :warning: |  |  |  |  |  |
| **OpenShift** | **4.13** | **4.14** | **4.15** | **4.16** | **4.17** | **4.18** |  |
|  | ❌ | ❌ | ✅ | ✅ | ✅ | ✅ |  |
| **VMware TKGI** | **1.16** | **1.17** | **1.18** | **1.19** | **1.20** |  |  |
|  |  | :warning: | :warning: | ✅ | ✅ |  |  |

title: Downloads

text:
- **Redis Enterprise**: `redislabs/redis:7.22.0-28`
- **Operator**: `redislabs/operator:7.22.0-7`
- **Services Rigger**: `redislabs/k8s-controller:7.22.0-7`
- **Call Home Client**: `redislabs/re-call-home-client:7.22.0-7`

title: Openshift downloads

text:
- **OLM operator bundle** : `7.22.0-7.0`
- **Call Home Client**: `redislabs/call-home-client:7.22.0-7`

title: Known limitations


title: Redis Enterprise for Kubernetes 7.22.0 release notes

summary: Releases with support for Redis Enterprise Software 7.22.0

title: Overview

text: Redis Enterprise for Kubernetes 7.22.0 includes bug fixes, enhancements, and support for Redis Enterprise Software. The latest release is 7.22.0-17 with support for Redis Enterprise Software version 7.22.0-250.

title: Detailed release notes

title: Supported distributions

text:
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 Kubernetes.

:warning: Deprecated – This distribution is still supported for this version of Redis Enterprise 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.28** | **1.29** | **1.30** | **1.31** | **1.32** | **1.33** |
|---|---|---|---|---|---|---|
| **Community K8s** |  |  | :warning: | ✅ | ✅ | ✅ |
| **Amazon EKS** |  |  | :warning: | ✅ | ✅ | ✅ |
| **Azure AKS** |  |  | :warning: | ✅ | ✅ | ✅ |
| **Google GKE** |  |  | :warning: | ✅ | ✅ | ✅ |
| **Rancher** | :warning: | ✅ | ✅ |  |  |  |
| **OpenShift** | **4.15** | **4.16** | **4.17** | **4.18** | **4.19** |  |
|  | :warning: | ✅ | ✅ | ✅ | ✅ |  |
| **VMware TKGI** | **1.19** | **1.20** | **1.21** |  |  |  |
|  | :warning: | ✅ | ✅ |  |  |  |

title: RHEL9-based image

text:
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]()

title: Known limitations

text:
- **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.

- **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.

- **Istio ingress does not support partial wildcard hostnames** When using Istio ingress for Redis on Kubernetes, avoid partial wildcard hostnames in your REC configuration. Use only valid FQDNs or leftmost wildcards for Istio compatibility and stable external routing. For more information, see [Istio Ingress Fails for Redis on Kubernetes with Partial Wildcard Hostnames](https://support.redislabs.com/hc/en-us/articles/30446436267666-Istio-Ingress-Fails-for-Redis-on-Kubernetes-with-Partial-Wildcard-Hostnames).

- **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.


title: Redis Enterprise for Kubernetes 7.22.2-21 (October 2025) release notes

summary: This is a maintenance release to support Redis Enterprise Software version 7.22.2-14.

title: Highlights

text: This is a maintenance release to support [Redis Enterprise Software version 7.22.2-14](). For version changes, supported distributions, and known limitations, see the [7.22.0 releases]().

title: Downloads

text:
- **Redis Enterprise**: `redislabs/redis:7.22.2-14`
- **Operator**: `redislabs/operator:7.22.2-21`
- **Services Rigger**: `redislabs/k8s-controller:7.22.2-21`
- **Call Home Client**: `redislabs/re-call-home-client:7.22.2-21`

title: Openshift downloads

text:
- **OLM operator bundle**: `v7.22.2-21.1`
- **Call Home Client**: `redislabs/call-home-client:7.22.2-21`

title: Known limitations

text: See [7.22.2 releases]() for information on known limitations.


title: Redis Enterprise for Kubernetes 7.22.2-22 (October 2025) release notes

summary: This is a maintenance release to support Redis Enterprise Software version 7.22.2-20.

title: Highlights

text: This is a maintenance release to support [Redis Enterprise Software version 7.22.2-20](). For version changes, supported distributions, and known limitations, see the [7.22.2 releases]().

title: Downloads

text:
- **Redis Enterprise**: `redislabs/redis:7.22.2-20`
- **Operator**: `redislabs/operator:7.22.2-22`
- **Services Rigger**: `redislabs/k8s-controller:7.22.2-22`
- **Call Home Client**: `redislabs/re-call-home-client:7.22.2-22`

title: Openshift downloads

text:
- **OLM operator bundle**: `v7.22.2-22.0`
- **Call Home Client**: `redislabs/call-home-client:7.22.2-22`

title: Known limitations


title: Redis Enterprise for Kubernetes 7.22.2-31 (December 2025) release notes

summary: Maintenance release to support Redis Enterprise Software version 7.22.2-41 including INE certificate support.

title: Highlights

text: This is a maintenance release to support [Redis Enterprise Software version 7.22.2-41](). For supported distributions known limitations, see the [7.22.2 releases]().

title: New in this release

title: Enhancements

text: - Added API fields to configure internode encryption certificates

title: Resolved issues

text: - Fixed upgrade issues with large clusters (RED-176468)

title: API changes

text:
| **CRD** | **Field** | **Change** | **Description** |
|---|---|---|---|
| REC | spec.dpInternodeEncryptionCertificateSecretName | Add | Secret name to use for cluster's Data Plane Internode Encryption (DPINE) certificate. If left blank, a cluster-provided certificate will be used. |
| REC | spec.cpInternodeEncryptionCertificateSecretName | Add | Secret name to use for cluster's Control Plane Internode Encryption (CPINE) certificate. If left blank, a cluster-provided certificate will be used. |

title: Deprecations

text: - The v1alpha1 API version of the RedisEnterpriseCluster (REC) custom resource is deprecated.

title: Downloads

text:
- **Redis Enterprise**: `redislabs/redis:7.22.2-41`
- **Operator**: `redislabs/operator:7.22.2-31`
- **Services Rigger**: `redislabs/k8s-controller:7.22.2-31`
- **Call Home Client**: `redislabs/re-call-home-client:7.22.2-31`

title: Openshift downloads

text:
- **OLM operator bundle**: `v7.22.2-31.1`
- **Call Home Client**: `redislabs/call-home-client:7.22.2-31`


title: Redis Enterprise for Kubernetes 7.22.2-32 (January 2026) release notes

summary: Maintenance release to support Redis Enterprise Software version 7.22.2-55 with bug and security fixes.

title: Highlights

text: This is a maintenance release to support Redis Enterprise Software version 7.22.2-55. For supported distributions and known limitations, see the [7.22.2 releases]().

title: Downloads

text:
- **Redis Enterprise**: `redislabs/redis:7.22.2-55`
- **Operator**: `redislabs/operator:7.22.2-32`
- **Services Rigger**: `redislabs/k8s-controller:7.22.2-32`
- **Call Home Client**: `redislabs/re-call-home-client:7.22.2-32`

title: Openshift downloads

text:
- **OLM operator bundle**: `v7.22.2-32.1`
- **Call Home Client**: `redislabs/call-home-client:7.22.2-32`

title: Known limitations


title: Redis Enterprise for Kubernetes 7.22.2-37 (February 2026) release notes

summary: Maintenance release to support Redis Enterprise Software version 7.22.2-79 with bug and security fixes.

title: Highlights

text: This is a maintenance release to support Redis Enterprise Software version 7.22.2-79. For supported distributions and known limitations, see the [7.22.2 releases]().

title: Downloads

text:
- **Redis Enterprise**: `redislabs/redis:7.22.2-79`
- **Operator**: `redislabs/operator:7.22.2-37`
- **Services Rigger**: `redislabs/k8s-controller:7.22.2-37`
- **Call Home Client**: `redislabs/re-call-home-client:7.22.2-37`

title: Openshift downloads

text:
- **OLM operator bundle**: `v7.22.2-37.1`
- **Call Home Client**: `redislabs/call-home-client:7.22.2-37`

title: Known limitations


title: Redis Enterprise for Kubernetes 7.22.2-38 (March 2026) release notes

summary: Maintenance release to support Redis Enterprise Software version 7.22.2-93 with bug and security fixes.

title: Highlights

text: This is a maintenance release to support Redis Enterprise Software version 7.22.2-93. For supported distributions and known limitations, see the [7.22.2 releases]().

title: Downloads

text:
- **Redis Enterprise**: `redislabs/redis:7.22.2-93`
- **Operator**: `redislabs/operator:7.22.2-38`
- **Services Rigger**: `redislabs/k8s-controller:7.22.2-38`
- **Call Home Client**: `redislabs/re-call-home-client:7.22.2-38`

title: Openshift downloads

text:
- **OLM operator bundle**: `v7.22.2-38.0`
- **Call Home Client**: `redislabs/call-home-client:7.22.2-38`

title: Known limitations

text: See [7.22.2 releases]() for information on known limitations.


title: Redis Enterprise for Kubernetes 7.22.2 release notes

summary: Releases with support for Redis Enterprise Software 7.22.2

title: Overview

text: Redis Enterprise for Kubernetes 7.22.2 includes bug fixes, enhancements, and support for Redis Enterprise Software. The latest release is 7.22.2-38 with support for Redis Enterprise Software version 7.22.2-93.

title: Detailed release notes

title: Known limitations

text: See [7.22.0 releases]() for information on known limitations.

title: RHEL9-based image

text:
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]()


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

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

title: Highlights

text: The primary purpose of this release is to support [Redis Enterprise 7.4.2](), which is a maintenance release of Redis Enterprise Software.

title: Version changes

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

title: Breaking changes

text:
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.

title: Deprecations

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

title: Supported distributions

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

title: Downloads

text:
- **Redis Enterprise**: `redislabs/redis:7.4.2-104`
- **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-104.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.6`

title: Known limitations

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