7.8.6-1

New in the release

Redis Enterprise for Kubernetes 7.8.6-1 is a feature release that includes enhancements, bug fixes, platform updates, and support for Redis Software 7.8.6-13. This release also includes the ability to install the operator using Helm (preview).

Enhancements

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

Resolved issues

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

API changes

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

Breaking changes

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

Supported distributions

The following table shows supported distributions at the time of this release. You can also find this list in [Supported Kubernetes distributions]({{< relref "/operate/kubernetes/reference/supported_k8s_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.26	1.27	1.28	1.29	1.30	1.31	1.32
Community K8s			❌	❌	✅	✅	✅
Amazon EKS			❌	⚠️	✅	✅	✅
Azure EKS			❌	⚠️	✅	✅	✅
Google GKE			❌	⚠️	✅	✅	✅
Rancher		❌	✅
VMware TKG 2.4	⚠️	⚠️	✅
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
		⚠️	⚠️	✅	✅

Downloads

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

Known limitations

See 7.8.6 releases for information on known limitations.

7.8.4-9

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

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

Supported distributions

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

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

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

❌ End of life – Support for this distribution ended.

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

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

Downloads

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

7.8.4-8

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

New in this release

Enhancements

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

Resolved issues

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

API changes

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

Supported distributions

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.25	1.26	1.27	1.28	1.29	1.30	1.31
Community Kubernetes			❌	✅	✅	✅	✅
Amazon EKS		❌	⚠️	✅	✅	✅
Azure AKS			⚠️	✅	✅	✅
Google GKE			❌	✅	✅	✅
Rancher RKE2		⚠️	✅	✅
VMware TKG 2.3		⚠️
VMware TKG 2.4		✅	✅
OpenShift	4.12	4.13	4.14	4.15	4.16
****	✅	✅	✅	✅	✅
VMWare TKGI	1.16	1.17	1.18	1.19
****	❌	✅	✅	✅

Downloads

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

7.8.2-6

Highlights

New in this release

Enhancements

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

Resolved issues

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

API changes

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

Version changes

Breaking changes

RHEL9-based images

• Redis Enterprise images are now based on Red Hat Enterprise Linux 9 (RHEL9). This means upgrades to 7.8.2-6 require:

• Cluster version of 7.4.2-2 or later.

• Database version 7.2 or later.

• RHEL9 compatible binaries for any modules you need.

See Upgrade Redis Enterprise for Kubernetes for detailed steps to upgrade to 7.8.2-6.

Deprecations

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

Supported distributions

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

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

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

❌ End of life – Support for this distribution ended.

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

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

Downloads

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

Known limitations

New limitations

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

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

Existing limitations

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

• The REDB “redisVersion” field can’t be used for memcached databases(RED-119152)

• 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-3746...

7.4.6-2

Highlights

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

New in this release

Enhancements

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

API changes

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

Version changes

Breaking changes

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

ValidatingWebhookConfiguration

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

OpenShift SCC

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

Upcoming Changes

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

Supported distributions

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

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

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

❌ End of life – Support for this distribution ended.

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

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

Downloads

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

OpenShift images

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

OLM bundle

Redis Enterprise operator bundle : v7.4.6-2.0

Known limitations

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

• The REDB “redisVersion” field can’t be used for memcached databases(RED-119152)

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

7.4.2-12

---

Highlights

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

New in this release

Enhancements

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

Resolved issues

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

API changes

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

Version changes

Breaking changes

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

ValidatingWebhookConfiguration

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

OpenShift SCC

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

Deprecations

• Redis Enterprise no longer supports Ubuntu-based images.

Upcoming Changes

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

Supported distributions

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

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

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

❌ End of life – Support for this distribution ended.

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

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

Downloads

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

OpenShift images

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

OLM bundle

Redis Enterprise operator bundle : v7.4.2-12.0

Known limitations

New limitations

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

Existing limitations

• The REDB “redisVersion” field can’t be used for memcached databases(RED-119152)

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

• **Clusters must be named 'rec' in OLM-based deployments (R...

7.4.2-2

Highlights

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

New in this release

Enhancements

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

Resolved issues

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

API changes

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

Version changes

Breaking changes

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

Upgrade operating system

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

terminationGracePeriodSeconds

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

ValidatingWebhookConfiguration

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

OpenShift SCC

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

Deprecations

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

Supported distributions

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.24	1.25	1.26	1.27	1.28	1.29
Community Kubernetes	❌	❌	⚠️	✅	✅	✅
Amazon EKS	⚠️	⚠️	✅	✅	✅
Azure AKS	❌	❌	⚠️	✅	✅
Google GKE	❌	⚠️	✅	✅	✅
Rancher RKE2	⚠️	✅	✅	✅
VMware TKG 2.2	⚠️	⚠️
VMware TKG 2.3	✅	✅	✅
VMware TKG 2.4		✅	✅	✅
OpenShift version	4.11	4.12	4.13	4.14
	⚠️	⚠️	✅	✅
VMware TKGI version	1.15	1.16	1.17	1.18
	✅	✅	✅	✅

Downloads

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

OpenShift images

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

OLM bundle

Redis Enterprise operator bundle : v7.4.2-2

Known limitations

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

New limitations

• The REDB “redisVersion” field can’t be used for memcached databases(RED-119152)

Existing limitations

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

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

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

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

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

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

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

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

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

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

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

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

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

• REC clusters fail to start on Kubernetes clusters with unsynchronized clocks (RED-47254) When REC cluste...

7.2.4-12

Highlights

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

New in this release

Enhancements

• Added to 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)

Resolved issues

• 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)

Version changes

Breaking changes

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.

Upcoming changes

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

Supported distributions

The following table shows supported distributions at the time of this release. You can also find this list in Supported Kubernetes distributions
✅ Supported – This distribution is supported for this version of Redis Enterprise Software for Kubernetes.

⚠️ 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
	❌	✅

Downloads

• 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

Known limitations

The limitations below are specific to the Redis Enterprise for Kubernetes product. To view limitations for the supported Redis Enterprise Software version, see the 7.2.4 release notes.

Existing limitations

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

• Clusters must be named 'rec' in OLM-based deployments (RED-39825) In OLM-deployed operators, the deployment of t...

7.2.4-7

Highlights

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.
• Added VMware TKG 2.1 and 2.2 to the Supported distributions table.

New in this release

Enhancements

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

Resolved issues

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

Version changes

Breaking changes

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.

Upcoming changes

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

Supported distributions

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

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

⚠️ 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
	❌	⚠️	✅	✅

Downloads

• 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

Known limitations

The limitations below are specific to the Redis Enterprise for Kubernetes product. To view limitations for the supported Redis Enterprise Software version, see the 7.2.4 release notes.

Existing limitations

• 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 pro...

7.2.4-2

Highlights

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 default engine, Speedb, for Auto Tiering (formerly Redis on Flash)

• Changes to supported Kubernetes distributions

New in this release

Enhancements

• 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)

Resolved issues

• 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)

API changes

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

Version changes

Breaking changes

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.

Deprecations

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

Supported distributions

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

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

⚠️ 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
	❌	⚠️	✅	✅

Downloads

• 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

{{}}
For users of Red Hat’s OLM installer, Redis is working with Red Hat on an upload issue that prevents the listing of this release in their OLM system. We will update any status or changes here. If this message is missing, then the issue has been resolved.
{{}}

Known limitations

The limitations below are specific to the Redis Enterprise for Kubernetes product. To view limitations for the supported Redis Enterprise Software version, see the 7.2.4 release notes.

New limitations

• Cannot upgrade or recover clusters if there are databases with modules that aren't built in (RED-107711 RED-106872) Contact support to upload your modules manually.

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

Existing limitations

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