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

Overview

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

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

Downloads

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

Openshift downloads

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


Redis Enterprise for Kubernetes 8.0.16 release notes

Summary: Releases with support for Redis Enterprise Software 8.0.16

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

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

Overview

Redis Enterprise for Kubernetes 8.0.16-24 is a maintenance release of Redis Enterprise for Kubernetes 8.0.10. The latest release is 8.0.16-24 with support for Redis Enterprise Software version 8.0.16-29.

Detailed release notes

Known limitations

New limitations

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

Existing limitations

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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


Redis Enterprise for Kubernetes 8.0.2-2 (October 2025) release notes

Summary: Feature release including support for Redis Software 8.0.2, enhancements, and bug fixes.

Overview

This feature release of Redis Enterprise for Kubernetes supports Redis Software 8.0.2-17 and includes enhancements, platform support changes, and bug fixes.

**Custom modules not supported**: If you use custom (user-defined) modules, skip this release. Custom module support will be available in the next release.

New in this release

This release includes enhancements to the Redis Enterprise for Kubernetes operator, and includes features supported by Redis Software 8.0.2-17, and Redis Open Source 8.0 and 8.2.

**Redis Enterprise for Kubernetes 8.0.2-2:**
This release includes enhancements to Redis Enterprise for Kubernetes including:

- Support for RS 8.0.2-17
- Support for the VKS platform (Broadcom/VMWare)
- Added container probes to Redis Enterprise pods
- Kubernetes 1.34 support (select platforms)
- Unique per release CSV/OperatorHub channels

**Redis Software 8.0.2-17:**

- Automatically enabled capabilities (modules) in Redis 8
- Metrics stream engine
- Module management enhancements
- Lag-aware availability API
- Redis Flex (Redis on Flash version 2)

For more information about Redis Software 8.0.2-17, see the [Redis Software 8.0.2-17 release notes]().

**Redis Open Source 8.0 and 8.2:**

- Preview of new vector set data type
- Redis query engine improvements
- Performance improvements
- Enhanced ACLs
- New hash and streams commands

For more details, see [What's new in Redis 8.0]() and [What's new in Redis 8.2](), and also the [Redis Open Source 8.0]() and [Redis Open Source 8.2]() release notes.

Resolved issues

- Fixed operator logs to properly reflect field inconsistencies between REC and statefulset (RED-161426)
- Applied security fixes (RED-162939, RED-163832, RED-165628, RED-168087)
- Fixed database tags being overridden when defined by Redis Software users (RED-170322)

API changes

| **CRD** | **Field** | **Change** | **Description** |
|---|---|---|---|
| REAADB | `spec.alertSettings.bdb_proxy_cert_expiring_soon` | Add | Enables a new alert in alert settings |
| REC | | Change | Changed the storage version of the API to v1 (from v1alpha1) |
| REDB | `spec.alertSettings.bdb_proxy_cert_expiring_soon` | Add | Enables a new alert in alert settings |
| REDB | `spec.moduleList` | Change | For Redis version 8 and later, bundled modules are enabled automatically, so you don't need to specify them |
| REDB | `spec.moduleList.[DbModule].version` | Change | Module versions in regular deployments are automatically selected by the Redis Enterprise cluster. Specified module versions are ignored. In Active-Active setups, you must specify the module version. |

Version changes

Modules in Redis 8

In Redis Enterprise databases created with or upgraded to Redis version 8 or later, bundled modules are enabled automatically, so you don't need to specify them in the `spec.moduleList` field. However, if you want to use a specific version of a bundled module, you can specify it in the `spec.moduleList` field.

The bundled capabilities (modules) are automatically enabled as follows:

| Database type | Automatically enabled capabilities |
|---------------|------------------------------------|
| RAM-only | [Search and query]()
[JSON]()
[Time series]()
[Probabilistic]()  |
| Flash-enabled ([Redis Flex]()) | [JSON]()
[Probabilistic]() |
| [Active-Active]() | [Search and query]()
[JSON]() |

For more information, see [Automatically enabled capabilities in Redis 8]().

Breaking changes

- **Custom modules are not supported** with this version. Only the capabilities (modules) listed above are supported in this release. **If you use user-defined modules, don't upgrade to this version.** The Redis Enterprise version used with this operator version includes significant changes to modules, including using built-in modules by default on databases. For more details, see the Redis Software release notes.

- **TKG (TKG) is no longer supported**. Broadcom/VMware doesn't plan to support this platform in the near future. We recommend that you migrate to TKGI/VKS.

For additional breaking changes related to Redis Software 8.0.2-17, see [Redis 8 breaking changes]().

Deprecations

- The RedisEnterpriseCluster (REC) v1alpha1 API version is deprecated.

Supported distributions

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

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

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

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

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

|  |  |  |  |  |  |  |  |
|---|---|---|---|---|---|---|---|
| Kubernetes version | **1.28** | **1.29** | **1.30** | **1.31** | **1.32** | **1.33** | **1.34** |
| **Community K8s** |  |  | ❌ | :warning: | ✅ | ✅ | ✅ |
| **Amazon EKS** |  |  | ❌ | :warning: | ✅ | ✅ | ✅ |
| **Azure EKS** |  |  | ❌ | :warning: | ✅ | ✅ | ✅ |
| **Google GKE** |  |  | ❌ | :warning: | ✅ | ✅ | ✅ |
| **Rancher REK2** | ❌ | :warning: | :warning: | ✅ | ✅ | ✅ |  |
| **VMware TKG 2.5** |  | ❌ | ❌ |  |  |  |  |
| **VMware VKS** |  |  |  |  | ✅ |  |  |
|  |  |  |  |  |  |  |  |
| **OpenShift** | **4.15** | **4.16** | **4.17** | **4.18** | **4.19** |  |  |
| --- | --- | --- | --- | --- | --- | --- | --- |
|  | ❌ | :warning: | ✅ | ✅ | ✅ |  |  |
|  |  |  |  |  |  |  |  |
| **VMware TKGI** | **1.19** | **1.20** | **1.21** | **1.22** |  |  |  |
| --- | --- | --- | --- | --- | --- | --- | --- |
|  | ❌ | :warning: | ✅ | ✅ |  |  |  |

Downloads

- **Redis Enterprise**: `redislabs/redis:8.0.2-17`
- **Operator**: `redislabs/operator:8.0.2-2`
- **Services Rigger**: `redislabs/k8s-controller:8.0.2-2`
- **Callhome client**: `redislabs/re-call-home-client:8.0.2-2`

Openshift downloads

- **OLM operator bundle** : `8.0.2-2.9`
- **Call Home Client**: `redislabs/call-home-client:8.0.2-2`

Known limitations

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

- **You must keep existing moduleList version numbers when upgrading redisVersion.** When upgrading a database's `redisVersion`, you must keep the existing module version numbers in `moduleList` unchanged. If you modify the module versions in `moduleList` during a `redisVersion` upgrade, the upgrade request will fail. The database will automatically use the bundled module versions for the new Redis version, regardless of what versions are specified in `moduleList`. This applies to both REDB and REAADB databases.

- **Custom certificate upload is not supported for internode encryption (RED-173229).** Internode communication between cluster nodes continues to use default self-signed certificates and cannot be configured with customer-provided certificates.

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

- **Database suffix changes during service-rigger termination cause resource recreation loops (RED-107687)** If you modify the database suffix for an Active-Active database while the service-rigger is in a terminating state, the service-rigger will continuously delete and recreate ingress or route resources. Wait until the services rigger pod has finished terminating before making suffix changes.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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


Redis Enterprise for Kubernetes 8.0.2-6 (December 2025) release notes

Summary: Maintenance release including support for Redis Software 8.0.2-41, enhancements, and bug fixes.

Overview

This maintenance release of Redis Enterprise for Kubernetes supports Redis Software 8.0.2-41 and includes enhancements, API changes, and bug fixes.

**Custom modules not supported**: If you use custom (user-defined) modules, skip this release. Custom module support will be available in the next release.

Enhancements

- Support for Redis Enterprise Software version 8.0.2-41
- Added API fields to configure internode encryption (RED-174881)

Resolved issues

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

API changes

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

Version changes

Modules in Redis 8

Breaking changes

- **Custom modules are not supported** with this version. Only the capabilities (modules) listed above are supported in this release. **If you use user-defined modules, don't upgrade to this version.** The Redis Enterprise version used with this operator version includes significant changes to modules, including using built-in modules by default on databases. For more details, see the Redis Software release notes.

- **TKG (TKG) is no longer supported**. Broadcom/VMware doesn't plan to support this platform in the near future. We recommend that you migrate to TKGI/VKS.

For additional breaking changes related to Redis Software 8.0.2-41, see [Redis 8 breaking changes]().

Deprecations

Supported distributions

Downloads

- **Redis Enterprise**: `redislabs/redis:8.0.2-41`
- **Operator**: `redislabs/operator:8.0.2-6`
- **Services Rigger**: `redislabs/k8s-controller:8.0.2-6`
- **Callhome client**: `redislabs/re-call-home-client:8.0.2-6`

Openshift downloads

- **OLM operator bundle** : `8.0.2-6.1`
- **Call Home Client**: `redislabs/call-home-client:8.0.2-6`

Known limitations

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

- **You must keep existing moduleList version numbers when upgrading redisVersion.** When upgrading a database's `redisVersion`, you must keep the existing module version numbers in `moduleList` unchanged. If you modify the module versions in `moduleList` during a `redisVersion` upgrade, the upgrade request will fail. The database will automatically use the bundled module versions for the new Redis version, regardless of what versions are specified in `moduleList`. This applies to both REDB and REAADB databases.

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

- **Database suffix changes during service-rigger termination cause resource recreation loops (RED-107687)** If you modify the database suffix for an Active-Active database while the service-rigger is in a terminating state, the service-rigger will continuously delete and recreate ingress or route resources. Wait until the services rigger pod has finished terminating before making suffix changes.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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


Redis Enterprise for Kubernetes 8.0.2 release notes

Summary: Releases with support for Redis Enterprise Software 8.0.2

Overview

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

Detailed release notes

RHEL9-based image

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

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

For detailed steps, see the relevant upgrade page:

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

Known limitations

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

- **Custom certificate upload is not supported for internode encryption (RED-173229).** Internode communication between cluster nodes continues to use default self-signed certificates and cannot be configured with customer-provided certificates.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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


Redis Enterprise for Kubernetes 8.0.6-8 (December 2025) release notes

Summary: Maintenance release including support for Redis Software 8.0.6-54, enhancements, and bug fixes.

Overview

Redis Enterprise for Kubernetes 8.0.6-8 is a feature release that supports Redis Software [8.0.6-54](), and includes enhancements, supported distribution updates and bug fixes.

Highlights

- Support for external module repositories (custom modules)
- Support for Redis Software [8.0.6-54]()
- SAML 2.0 single sign-on (SSO) authentication support for the cluster manager UI

Enhancements

API support has been added for the following features:

- Database connection auditing<!--RED-166368-->
- REAADB alerts<!--RED-170896-->
- User-defined modules <!--RED-168227-->
- Redis Software [8.0.6-54]() <!--RED-172935-->
- User-defined certificates for [internode encryption]() <!--RED-173229-->
- SAML 2.0 single sign-on (SSO) authentication <!--RED-176765-->
- Redis Flex

See [API changes](#api-changes) for details.

Resolved issues

- Removed 'InsecureRequestWarning: Unverified HTTPS request is being made to host localhost' message that appeared when running the healthcheck script <!--RED-71858-->
- Fixed bug that blocked image spec updates during active REC upgrades. <!--RED-84166-->
- Fixed slow reaction time by services-rigger to node failures. <!--RED-174164-->
- Fixed operator syncing REAADB in a loop when S3 backup is enabled <!--RED-173464-->
- Security patches

API changes

| **CRD** | **Field** | **Change** | **Description** |
|---|---|---|---|
| REAADB | `spec.globalConfigurations.auditing` | Added | Enable database connection auditing. |
| REAADB | `spec.globalConfigurations.alertSettings` | Added | Configure alert settings for the active-active database. |
| REAADB | `spec.globalConfigurations.rofRamRatio` | Added | RAM allocation ratio for Redis Flex (v2) databases as a percentage of total data size. Valid range: 0-100. Default: 50% when omitted. Controls how much RAM is allocated per unit of data (for example, 30% means 3MB RAM per 10MB data). RAM grows proportionally with data until `rofRamSize` limit is reached (if specified). Only applicable when `isRof=true` and Redis version 8.0 or later (BigStore v2 - Redis Flex). |
| REC | `spec.auditing` | Added | Cluster-level configuration for auditing database connection and authentication events. Includes both the audit listener connection parameters and the default policy for new databases. |
| REC | `spec.sso` | Added | Cluster-level SSO configuration for authentication to the cluster manager UI. |
| REC | `spec.userDefinedModules` | Added | List of user-defined modules to be downloaded and installed during cluster bootstrap. The modules on the list will be downloaded on cluster creation, upgrade, scale-out, and recovery and installed on all nodes. Changing this field for a running cluster will trigger a rolling update. |
| REC | `spec.certificates.ssoServiceCertificateSecretName` | Added | Secret name for the cluster's SSO service certificate. Used for SAML-based SSO authentication to the cluster manager. The secret must contain `name`, `certificate`, and `key` fields (same format as other cluster certificates). If left blank, SSO will not be configured. |
| REC | `spec.certificates.ssoIssuerCertificateSecretName` | Added | Secret name for the SSO Identity Provider (IdP) certificate. This is the public certificate from your SAML Identity Provider used to verify SAML assertions. The secret must contain `name` and `certificate` fields (no `key` field needed for IdP certificate). This is optional - if using IdP metadata XML, the IdP certificate is included in the metadata. |
| REDB | `spec.auditing` | Added | Database-level auditing configuration. |
| REDB | `spec.rofRamRatio` | Added | RAM allocation ratio for Redis Flex (v2) databases as a percentage of total data size. Valid range: 0-100. Default: 50% when omitted. Controls how much RAM is allocated per unit of data (for example, 30% means 3MB RAM per 10MB data). RAM grows proportionally with data until `rofRamSize` limit is reached (if specified). Only applicable when `isRof=true` and Redis version 8.0 or later (BigStore v2 - Redis Flex). |
| REDB | `status.bigstoreVersion` | Added | BigStore version for Redis on Flash databases (1 for Auto Tiering, 2 for Redis Flex). Read-only field populated from Redis Software. |

Supported distributions

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

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

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

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

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

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

Downloads

- **Redis Enterprise**: `redislabs/redis:8.0.6-54`
- **Operator**: `redislabs/operator:8.0.6-8`
- **Services Rigger**: `redislabs/k8s-controller:8.0.6-8`
- **Callhome client**: `redislabs/re-call-home-client:8.0.6-8`

Openshift downloads

- **OLM operator bundle**: `8.0.6-8.0`
- **Call Home Client**: `redislabs/call-home-client:8.0.6-8`

Known limitations

New limitations

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

Existing limitations

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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


Redis Enterprise for Kubernetes 8.0.6 release notes

Summary: Releases with support for Redis Enterprise Software 8.0.6

Overview

Redis Enterprise for Kubernetes 8.0.6 includes bug fixes, enhancements, and support for Redis Enterprise Software 8.0.6. The latest release is 8.0.6-8 with support for Redis Enterprise Software version 8.0.6-54.

Detailed release notes

Known limitations

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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


Redis Enterprise Software for Kubernetes release notes

Summary: Redis Enterprise Software for Kubernetes operator release notes.

Summary: Releases with support for Redis Enterprise Software 8.0.10

Redis Enterprise for Kubernetes 8.0.10 release notes

Summary: Releases with support for Redis Enterprise Software 7.22.2

Redis Enterprise for Kubernetes 7.22.2 release notes

Summary: Releases with support for Redis Enterprise Software 7.22.0

Redis Enterprise for Kubernetes 7.22.0 release notes

Summary: Release notes for versions of Redis Enterprise for Kubernetes released more than 18 months ago.

Previous version Redis Enterprise for Kubernetes release notes

Summary: Releases with support for Redis Enterprise Software 7.8.6

Redis Enterprise for Kubernetes 7.8.6 release notes

Summary: Releases with support for Redis Enterprise Software 7.8.4

Redis Enterprise for Kubernetes 7.8.4 release notes

Summary: Releases with support for Redis Enterprise Software 7.8.2

Redis Enterprise for Kubernetes 7.8.2-6 release notes

Summary: Releases with support for Redis Enterprise Software 7.4.6.

Redis Enterprise for Kubernetes 7.4.6 release notes

Summary: Releases with support for Redis Enterprise Software 7.4.2.

Redis Enterprise for Kubernetes 7.4.2 release notes

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

7.2.4 release notes

Summary: Release notes for the 6.4.2 releases of Redis Enterprise Software for Kubernetes.

6.4.2 release notes

Summary: Release notes for the 6.2.x releases of Redis Enterprise Software for Kubernetes.

6.2.18 release notes


Summary: Support for RS 6.0.20-97, EKS, Hashicorp Vault, and added feature support for OpenShift OLM.

Redis Enterprise for Kubernetes Release Notes 6.0.20-12 (July 2021)

Summary: Support for 6.0.20-69, OpenShift 4.7, and K8s 1.20. Hashicorp Vault integration with REC and REDB secrets.

Redis Enterprise for Kubernetes Release Notes 6.0.20-4 (May 2021)

Summary: Support for RS 6.0.12-57, Amazon Kubernetes Service (AKS), and role permissions on custom resources.

Redis Enterprise for Kubernetes Release Notes 6.0.12-5 (February 2021)

Summary: Support for RS 6.0.8, consumer namespaces, Gesher admission controller proxy, and custom resource validation via schema.

Redis Enterprise for Kubernetes Release Notes 6.0.8-20 (December 2020)

Summary: Support for RS 6.0.8-28, OpenShift 4.5, K8s 1.18, and Gesher admission controller proxy.

Redis Enterprise for Kubernetes Release Notes 6.0.8-1 (October 2020)

Summary: Various bug fixes.

Redis Enterprise for Kubernetes Release Notes 6.0.6-24 (August 2020)

Summary: Support for Redis Enterprise Software 6.0.6-39, Rancher support, new database backup and alert options.

Redis Enterprise for Kubernetes Release Notes 6.0.6-23 (August 2020)

Summary: Maintenance release; support RS 6.0.6-39 and various bug fixes.

Redis Enterprise for Kubernetes Release Notes 6.0.6-11 (July 2020)

Summary: Support for RS 6.0.6, new database and admission controllers, various improvements and bug fixes.

Redis Enterprise for Kubernetes Release Notes 6.0.6-6 (June 2020)

Summary: Support for Redis Enterprise Software 5.4.14, K8s 1.16, and OpenShift 4.3.

Redis Enterprise for Kubernetes Release Notes 5.4.14-2 (March 2020)

Summary: Support for the Redis Enterprise Software 5.4.10 and multiple enhancements.

Redis Enterprise for Kubernetes Release Notes 5.4.10-8 (January 2020)

Content

Below are archived release notes for Redis Enterprise for Kubernetes versions released more than 18 months ago.


Overview

[Redis Enterprise for Kubernetes 5.4.10-8](https://github.com/RedisLabs/redis-enterprise-k8s-docs/releases/tag/5.4.10-8) is now available.
This release includes Redis Enterprise (RS) version [5.4.10-22]() and introduces new feature and bug fixes.

Overview

This is a maintenance release providing support for the Redis Enterprise Software release 5.4.10 and includes multiple enhancements.

Follow these [instructions]() for upgrading to this Kubernetes operator release.

New features

- All-in-one deployment bundle and documentation enhancements - This release is the easiest to deploy yet, with a new quick start guide and an all-in-one file bundle for deploying the Redis Enterprise Operator. GitHub documentation was enhanced to cover advanced deployment scenarios with the complete reference to the custom resource specifications, guides, and examples.

    Pay special attention to the yaml file naming changes and new yaml files that have been created for this release. These are highlighted in the quick start guide.

- Rack Awareness - Support for the [Redis Software Rack Awareness][] feature was introduced to the Kubernetes deployment. It enables deploying nodes to different zones, in a multi-zone Kubernetes cluster. Databases that are rack-aware will have the cluster populate their master shard and replica shards in different nodes, across different zones or failure domains. This enables maintaining data persistence in case of zone failure.

- OLM Support - Redis Enterprise for Kubernetes is now RedHat OpenShift certified and can be effortlessly configured and deployed in Kubernetes clusters supporting OLM, including OpenShift 4.x clusters, with just a few clicks. OLM based deployments do not require Kubernetes cluster administrator rights to deploy the operator.

- Improve cluster nodes' pod scheduling resiliency - Redis Enterprise Cluster pod scheduling is hardened by implementing Kubernetes best practices and providing configuration recommendations to cluster operators. Scheduling resiliency minimizes the chance of cluster node pods eviction or failure to schedule.
See the top 4 articles in the new [Additonal Topics](https://github.com/RedisLabs/redis-enterprise-k8s-docs/blob/92a2eff4b8c4ccafac459138f12e5f38acde825c/docs/topics.md#additional-topics) documentation section.

- Update app.redislabs.com API version to stable - We've updated the Redis Enterprise Cluster custom resource API from [alpha to stable](https://kubernetes.io/docs/concepts/overview/kubernetes-api/#api-versioning) to reflect the current state of maturity of our implementation.

[Both versions of the API are supported](https://kubernetes.io/docs/tasks/extend-kubernetes/custom-resources/custom-resource-definition-versioning/) by Kubernetes versions that support specifying multiple API versions.

For legacy Kubernetes versions, deployment files are available in the documentation repository that utilize the alpha version of the API.

Information

- This new release deprecates the Redis Enterprise Operator support for legacy Kubernetes version 1.8.

Known limitations

- Custom Resource Definition Changes - In order to comply with OLM best practices, a change was required to the Redis Enterprise Cluster Custom Resource Defintion (CRD) to introduce the status sub-resource.
As a result of this change, any upgrade from an older release to this release requires a change to the CRD. Once the CRD is updated, all Redis Enterprise Clusters in the same K8s cluster must be updated to the latest release in order to continue operating properly.

- Cluster Recovery -


Overview

The Redis Enterprise K8s 5.4.14-2 release is a maintenance release providing support for the latest Redis Enterprise Software release 5.4.14 and includes bug fixes as well as the following notable changes:

Support for K8s 1.16

This release now correctly handles the API deprecations, and API version changes that K8s release 1.16 introduced.

Support for OpenShift 4.3; improved OLM support

The release now supports OpenShift 4.3. A new operator version is now available in OpenShift's Operator Hub and now includes a more comprehensive base template as well as references to documentation and support.

Changes to the upgrade process

When the Operator is upgraded to a new release, it now prevents the Redis Enterprise Cluster nodes from being automatically upgraded, unless autoUpgrade is enabled or the RS image version is explicitly updated in the Redis Enterprise Cluster (REC) spec. The change was introduced to avoid situations where an Operator upgrade initiated a rolling update to the cluster nodes' StatefulSet.

Deprecated support for K8s versions 1.9/1.10

This release deprecates support for K8s version 1.9/1.10 and OpenShift 3.9. If you are currently using these releases please contact Redis support for information about migrating to a new K8s release.

Coming soon

- The Database Custom Resource(CR), which represents Redis Enterprise databases, is in development and planned to be part of an upcoming release. The Database Controller for the Database CR is part of the Redis Enterprise K8s Operator. It is disabled in this release.
- The next release is planned to support K8s 1.17 and drop support for K8s versions 1.9/1.10.


Overview

The Redis Enterprise [K8s 6.0.12-5](https://github.com/RedisLabs/redis-enterprise-k8s-docs/releases/tag/v6.0.12-5) release is a *major release* on top of [6.0.8-20](https://github.com/RedisLabs/redis-enterprise-k8s-docs/releases/tag/v6.0.8-20) providing support for the [Redis Enterprise Software release 6.0.12-57](https://docs.redislabs.com/latest/rs/release-notes/rs-6-0-12-january-2021/) and includes several enhancements and bug fixes.

Overview

This release of the operator provides:

 * New features
 * Various bug fixes

To upgrade your deployment to this latest release, see ["Upgrade a Redis Enterprise cluster (REC) on Kubernetes"]().

Images

This release includes the following container images:
 * **Redis Enterprise**: redislabs/redis:6.0.12-57 or redislabs/redis:6.0.12-57.rhel7-openshift
 * **Operator and Bootstrapper**: redislabs/operator:6.0.12-5
 * **Services Rigger**: redislabs/k8s-controller:6.0.12-5 or redislabs/services-manager:6.0.12-5 (Red Hat registry)

New features

* [Azure Kubernetes Service](https://azure.microsoft.com/en-us/services/kubernetes-service/) (AKS) is now supported. (RED40323)
 * Database custom resources now support roles permissions (role to Redis ACL bindings). (RED49780)

Feature Improvements

* The license information has been added to the REC status. (RED43078)
 * `kubectl get rec` now displays more information (i.e., added "NODES", "VERSION", "STATE", "SPEC STATUS"). (RED46428)
 * The `extraLabels` in the cluster spec now applies to the PV and PVC at creation. (RED48694)
 * Added [Rancher 2.5](https://rancher.com/products/rancher/2.5) support. (RED50211)
 * Added K8s (Kops) 1.19 support. (RED50211)
 * Added [OpenShift 4.6](https://docs.openshift.com/container-platform/4.6/welcome/index.html) support. (RED50495)
 * Database resources can now disable the default database user. (RED50215)
 * REC credentials no longer use environment variables in pods. (RED47969)

Important fixes

* Fixed an issue where pods are stuck terminating during teardown. (RED44726)
 * Fixed an issue where pods are stuck terminating during cluster recovery. (RED43846)
 * Changed the operator logs to use human-readable dates and times. (RED39026)
 * Fixed the display of resources in the OLM (OpenShift). (RED48116)
 * Fixed backup configuration issue for GCS without a subdir. (RED49299)

Known limitations

CrashLoopBackOff causes cluster recovery to be incomplete  (RED33713)

When a pod's status is `CrashLoopBackOff` and we run the cluster recovery, the process will not complete. The workaround is to delete the crashing pods manually. The recovery process will then continue.

Long cluster names cause routes to be rejected  (RED25871)

A cluster name longer than 20 characters will result in a rejected route configuration because the host part of the domain name will exceed 63 characters. The workaround is to limit cluster name to 20 characters or fewer.

Cluster CR (REC) errors are not reported after invalid updates (RED25542)

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 (RED32805)

When a cluster is in an unreachable state, the state is still `running` instead of being reported as an error.

Readiness probe incorrect on failures (RED39300)

STS Readiness probe does not mark a node as "not ready" when running `rladmin status` on the node fails.

Role missing on replica sets (RED39002)

The `redis-enterprise-operator` role is missing permission on replica sets.

Private registries are not supported on OpenShift 3.11 (RED38579)

Openshift 3.11 does not support DockerHub private registries. This is a known OpenShift issue.

Internal DNS and Kubernetes DNS may have conflicts (RED37462)

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 (RED37233)

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 (RED36884)

In Kubernetes, the node CPU usage we report on is the usage of the Kubernetes worker node hosting the REC pod.

Clusters must be named "rec" in OLM-based deployments (RED39825)

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) is bound to a specific service account name (i.e., "rec"). The workaround is to name the cluster "rec".

Master pod label in Rancher (RED42896)

The master pod is not always labeled in Rancher.

REC clusters fail to start on Kubernetes clusters with unsynchronized clocks (RED47254)

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 (RED47192)

When a 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. As such, until the
REDB resources are deleted, the project deletion will hang. The fix is to delete the
REDB resources first and the REC second. Afterwards, you may delete the project.

REC extraLabels are not applied to PVCs on K8s versions 1.15 or older (RED51921)

In K8s 1.15 or older, the PVC labels come from the match selectors and not the
PVC templates. As such, these versions can not support PVC labels. If this feature
is required, the only fix is to upgrade the K8s cluster to a newer version.

Compatibility Notes

* OpenShift 4.6 and Rancher/kOps 1.19 are now supported.
 * Rancher 2.5 is now supported.
 * AKS (K8s 1.18) is now supported.

Deprecation notice

* OpenShift 4.1, 4.2, and 4.3 are now deprecated.
 * GKE K8s version 1.14 is deprecated.
 * kOps 1.13 and 1.14 are deprecated.


Redis Enterprise for Kubernetes Release Notes 6.0.20-12 (July 2021)

Overview

The Redis Enterprise [K8s 6.0.20-12](https://github.com/RedisLabs/redis-enterprise-k8s-docs/releases/tag/v6.0.20-12) release is a *major release* on top of [6.0.20-4](https://github.com/RedisLabs/redis-enterprise-k8s-docs/releases/tag/v6.0.20-4) providing support for the [Redis Enterprise Software release 6.0.20-97](https://docs.redislabs.com/latest/rs/release-notes/rs-6-0-20-april-2021/) and includes several enhancements and bug fixes.

This release of the operator provides:

* New features
* Various bug fixes

Images

This release includes the following container images:

* **Redis Enterprise**: `redislabs/redis:6.0.20-97` or  redislabs/redis:6.0.20-97.rhel7-openshift`
* **Operator and Bootstrapper**: `redislabs/operator:6.0.20-12`
* **Services Rigger**: `redislabs/k8s-controller:6.0.20-12` or `redislabs/services-manager:6.0.20-12` (on the Red Hat registry)

New features

* EKS support
* Feature parity for Openshift OLM; added support for:
   - REDB
   - admission
   - Hashicorp Vault integration
* Hashicorp Vault integration is now GA
* Moved Operator environment variables to configmap

Important fixes

* Admission controller deployment combined with operator deployment to simplify deployment (RED-52701)
* Additional verbosity in the `kubectl get redb` command output (RED-55042)
* Support for Redis Enterprise license storage within secrets; Vault and K8s secrets (RED-55587)
* Support for manual procedure to replace the REC credentials (RED-56529, RED-56530)
* Fixed cluster recovery issue - recovery process was not starting (RED-55500)
* When a pod status is CrashLoopBackOff and we run the cluster recovery, the process will not complete (RED-33713)
* Master pod is not always labeled in Rancher (fixed in 6.0.8 but was not documented) (RED-42896)

Known limitations

Hashicorp Vault integration - no support for Gesher (RED-55080)

There is no workaround at this time

Nodes down indefinitely after the redis-enterprise-node container of a REC pod is restarted (53042)

In some cases where the Redis Enterprise Cluster container in the Redis Enterprise Cluster(REC) pod is restarted, the REC node remains down. Workaround: restart the pod, while ensuring the majority of REC nodes are available.

When a pod's status is `CrashLoopBackOff` and we run the cluster recovery, the process will not complete. The workaround is to delete the crashing pods manually. The recovery process will then continue.

A cluster name longer than 20 characters will result in a rejected route configuration because the host part of the domain name will exceed 63 characters. The workaround is to limit cluster name to 20 characters or fewer.

A cluster CR specification error is not reported if two or more invalid CR resources are updated in sequence.

When a cluster is in an unreachable state, the state is still `running` instead of being reported as an error.

STS Readiness probe does not mark a node as "not ready" when running `rladmin status` on the node fails.

Role missing on replica sets (RED39002)

The `redis-enterprise-operator` role is missing permission on replica sets.

Openshift 3.11 does not support DockerHub private registries. This is a known OpenShift issue.

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.

Kubernetes-based 5.4.10 deployments seem to negatively impact existing 5.4.6 deployments that share a Kubernetes cluster.

In Kubernetes, the node CPU usage we report on is the usage of the Kubernetes worker node hosting the REC pod.

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) is bound to a specific service account name (i.e., "rec"). The workaround is to name the cluster "rec".

Master pod label in Rancher (RED42896)

The master pod is not always labeled in Rancher.

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.

When a 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. As such, until the
REDB resources are deleted, the project deletion will hang. The fix is to delete the
REDB resources first and the REC second. Afterwards, you may delete the project.

In K8s 1.15 or older, the PVC labels come from the match selectors and not the
PVC templates. As such, these versions can not support PVC labels. If this feature
is required, the only fix is to upgrade the K8s cluster to a newer version.

Compatibility Notes

* EKS is now supported (K8s 1.18)
* OpenShift 4.4 (previously deprecated) is no longer supported
* GKE K8s versions 1.15, 1.16 (previously deprecated) is no longer supported
* VMWare TKGI 1.10 (K8s 1.19) is now supported

Deprecation notice

* GKE K8s version 1.17 (no longer supported by Google) is deprecated
* kOps 1.15 is deprecated
* VMWare TKGI 1.7 (K8s 1.16), VMWare TKGI 1.8 (K8s 1.17) are deprecated (no longer supported by VMWare)


Redis Enterprise for Kubernetes Release Notes 6.0.20-4 (May 2021)

Overview

The Redis Enterprise K8s [6.0.20-4](https://github.com/RedisLabs/redis-enterprise-k8s-docs/releases/tag/v6.0.20-4) release is a *major release* on top of [6.0.8-20](https://github.com/RedisLabs/redis-enterprise-k8s-docs/releases/tag/v6.0.8-20) providing support for the [Redis Enterprise Software release 6.0.20-69]() and includes several enhancements and bug fixes.

Overview

This release of the operator provides:
 * New features
 * Various bug fixes

To upgrade your deployment to this latest release, see ["Upgrade a Redis Enterprise cluster (REC) on Kubernetes"]().

Images

This release includes the following container images:
 * **Redis Enterprise**: redislabs/redis:6.0.20-69 or redislabs/redis:6.0.20-69.rhel7-openshift
 * **Operator and Bootstrapper**: redislabs/operator:6.0.20-4
 * **Services Rigger**: redislabs/k8s-controller:6.0.20-4 or redislabs/services-manager:6.0.20-4 (on the Red Hat registry)

New features

* Support for Openshift 4.7
 * Support for Kubernetes 1.20

 ## New preview features
 * Hashicorp Vault integration - REC secret
 * Hashicorp Vault integration - REDB secrets

Important fixes

- Fixed upgrade issue with custom container repositories specifying port numbers (RED-53192)
- REDB controller no longer performs reconciliation until Redis Enterprise software version complies with operator (RED-53194)
- Removed unused node.js package from Services Rigger image (RED-53536)
- Fixed operator crash on change of uiServiceType (RED-54621)
- Avoid excessive logging within RS pod (envoy_access.log) (RED-55525)

Known limitations

OpenShift 4.7 - v6.0.20-4 cannot be deployed by OLM

6.0.20-4 does not appear in OLM. Workaround - deploy manually. A future maintenance release will address this.

There is no workaround at this time

In some cases where the Redis Enterprise Cluster container in the Redis Enterprise Cluster(REC) pod is restarted, the REC node remains down. Workaround: restart the pod, while ensuring the majority of REC nodes are available.

CrashLoopBackOff causes cluster recovery to be incomplete  (RED33713)

When a pod's status is `CrashLoopBackOff` and we run the cluster recovery, the process will not complete. The workaround is to delete the crashing pods manually. The recovery process will then continue.

Long cluster names cause routes to be rejected  (RED25871)

A cluster name longer than 20 characters will result in a rejected route configuration because the host part of the domain name will exceed 63 characters. The workaround is to limit cluster name to 20 characters or fewer.

Cluster CR (REC) errors are not reported after invalid updates (RED25542)

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 (RED32805)

When a cluster is in an unreachable state, the state is still `running` instead of being reported as an error.

Readiness probe incorrect on failures (RED39300)

STS Readiness probe does not mark a node as "not ready" when running `rladmin status` on the node fails.

Role missing on replica sets (RED39002)

The `redis-enterprise-operator` role is missing permission on replica sets.

Private registries are not supported on OpenShift 3.11 (RED38579)

Openshift 3.11 does not support DockerHub private registries. This is a known OpenShift issue.

Internal DNS and Kubernetes DNS may have conflicts (RED37462)

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 (RED37233)

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 (RED36884)

In Kubernetes, the node CPU usage we report on is the usage of the Kubernetes worker node hosting the REC pod.

Clusters must be named "rec" in OLM-based deployments (RED39825)

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) is bound to a specific service account name (i.e., "rec"). The workaround is to name the cluster "rec".

Master pod label in Rancher (RED42896)

The master pod is not always labeled in Rancher.

REC clusters fail to start on Kubernetes clusters with unsynchronized clocks (RED47254)

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 (RED47192)

When a 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. As such, until the
REDB resources are deleted, the project deletion will hang. The fix is to delete the
REDB resources first and the REC second. Afterwards, you may delete the project.

REC extraLabels are not applied to PVCs on K8s versions 1.15 or older (RED51921)

In K8s 1.15 or older, the PVC labels come from the match selectors and not the
PVC templates. As such, these versions can not support PVC labels. If this feature
is required, the only fix is to upgrade the K8s cluster to a newer version.

Compatability Notes

- OpenShift 4.7 and Rancher/kOps 1.20 are now supported
- OpenShift 4.1, 4.2, 4.3 (previously deprecated) are no longer supported
- GKE K8s version 1.14 (previously deprecated) is no longer supported
- kOps (upstream K8s) 1.13, 1.14 (previously deprecated) are no longer supported

Deprecation notice

- OpenShift 4.4 (no longer supported by Red Hat) is deprecated
- GKE K8s versions 1.15, 1.16 (no longer supported by Google) are deprecated
- kOps (upstream K8s) 1.15 is deprecated


Redis Enterprise for Kubernetes Release Notes 6.0.6-11 (July 2020)

Overview

The Redis Enterprise K8s 6.0.6-11 release is a *maintenance release* on top of [6.0.6-6](https://github.com/RedisLabs/redis-enterprise-k8s-docs/releases/tag/v6.0.6-6) providing support for the latest [Redis Enterprise Software release 6.0.6-39](https://docs.redislabs.com/latest/rs/release-notes/rs-6-0-may-2020/) and includes several bug fixes.

Overview

This release of the operator provides:

- Support for the Redis Enterprise Software release 6.0.6-39
- Various bug fixes

To upgrade your deployment to this latest release, see ["Upgrade a Redis Enterprise cluster (REC) on Kubernetes"]().

Images

- **Redis Enterprise** - redislabs/redis:6.0.6-39 or redislabs/redis:6.0.6-39.rhel7-openshift
- **Operator** - redislabs/operator:6.0.6-11 or redislabs/operator:6.0.6-11.rhel7
- **Services Rigger** - redislabs/k8s-controller:6.0.6-11 or redislabs/k8s-controller:6.0.6-11.rhel7

Important fixes

- The upgrade process may have failed in certain situations (i.e., with CRDB databases). We now ensure that rlutil runs at bootstrap to complete the upgrade process. (RED43635)
- The example and default custom resource for the REC in the OLM now correctly uses 'nodes' (RED43847)
- Fixes for security vulnerabilities in the server rigger image: upgraded to httpd 2.4.42, Kubernetes Python Client 8.0.1, and removed localhost private key. (RED42495)
- A fix for an internal logging issue that caused errors to incorrectly show up on the operator log when databases are created even though the creation succeeded. (RED43336)

Known limitations

- CrashLoopBackOff causes cluster recovery to be incomplete  (RED33713) - When a pod status is CrashLoopBackOff and we run the cluster recovery, the process will not complete. The solution is to delete the crashing pods manually and recovery process will continue.

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

- No cleanup of database services on failures (RED25825) - The service broker doesn't clean up database service bindings when there are failures. The workaround is to manually remove service bindings.

- Server broker errors with two service naming schemes  (RED25547) - The service broker deployment results in an error when two types of service naming schemes are set. You must choose one of the methods if both are set - redis-port is the recommended default.

- Cluster CR (REC) errors are not reported after invalid updates (RED25542) - 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 (RED32805) - When a cluster is in an unreachable state the state is still running instead of being reported as an error.

- Readiness probe incorrect on failures (RED39300) - STS Readiness probe doesn't mark a node as not ready when rladmin status on the node fails

- Role missing on replica sets (RED39002) - The redis-enterprise-operator role is missing permission on replica sets.

- Private registries are not supported on OpenShift 3.11 (RED38579) - Openshift 3.11 doesn't support dockerhub private registry. This is a known OpenShift issue.

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

- 5.4.10 negatively impacts 5.4.6 (RED37233) - K8S-based 5.4.10 clusters seem to negatively affect existing 5.4.6

- Node CPU usage is reported instead of pod CPU usage (RED36884) - In Kubernetes, the node CPU usage we report on is the usage of the K8S worker node hosting the REC pod.

- Clusters must be named "rec" in OLM-based deployments (RED39825) - 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) is bound to a specific service account name (i.e., "rec"). The workaround is to name the cluster "rec".


Redis Enterprise for Kubernetes Release Notes 6.0.6-23 (August 2020)

Overview

The Redis Enterprise K8s 6.0.6-23 release is a *major release* on top of [6.0.6-11](https://github.com/RedisLabs/redis-enterprise-k8s-docs/releases/tag/v6.0.6-11) providing support for the latest [Redis Enterprise Software release 6.0.6-39](https://docs.redislabs.com/latest/rs/release-notes/rs-6-0-may-2020/) and includes several enhancements (including Rancher support) and bug fixes.

Overview

This release of the operator provides:

- Support for the Redis Enterprise Software release 6.0.6-39
- Support for Rancher
- Backup options in the database custom resource and controller
- Alert option in the database custom resource and controller
- UBI images
- Various other enhancements and bug fixes

To upgrade your deployment to this latest release, see ["Upgrade a Redis Enterprise cluster (REC) on Kubernetes"]().

Images

- **Redis Enterprise** - redislabs/redis:6.0.6-39 or redislabs/redis:6.0.6-39.rhel7-openshift
- **Operator** - redislabs/operator:6.0.6-23
- **Services Rigger** - redislabs/k8s-controller:6.0.6-23 or redislabs/services-manager:6.0.6-23 (on the RedHat registry)

New features

Red Hat UBI base images (RED29651) - The services rigger and operator images are now based on Red Hat UBI base images. Also, the same images are now used in both OpenShift and non-OpenShift environments.

- Rancher support (RED37918) - The operator is now supported on [Rancher](https://rancher.com/) version ([v2.4.5](https://rancher.com/support-maintenance-terms/all-supported-versions/rancher-v2.4.5/)). Note that since this release of the operator doesn't support K8s 1.18, it requires one of the other supported upstread version in this Rancher release, i.e. 1.15.12, 1.16.13 or 1.17.9.

- Database Replica Of support (RED40160) - Support for [Replica Of](https://docs.redislabs.com/latest/rs/administering/active-passive/) was added to the [DB controller](https://github.com/RedisLabs/redis-enterprise-k8s-docs/blob/master/redis_enterprise_database_api.md#replicasource).

- Database backup configuration (RED40165) - Support for [backup configuration](https://docs.redislabs.com/latest/rs/administering/database-operations/database-backup/) was added to the [DB controller spec](https://github.com/RedisLabs/redis-enterprise-k8s-docs/blob/master/redis_enterprise_database_api.md#backupspec).

- Alert configuration (RED40166) - Support for alert configuration was added to the [DB controller spec](https://github.com/RedisLabs/redis-enterprise-k8s-docs/blob/master/redis_enterprise_database_api.md#dbalertssettings).

- Database TLS configuration (RED41758) - Support for TLS authentication configuration was added to the [DB controller spec](https://github.com/RedisLabs/redis-enterprise-k8s-docs/blob/0ec741ffb3d621d371b5eec5b0a045ee7364e50e/redis_enterprise_database_api.md#redisenterprisedatabasespec).

- OpenShift 4.4 support (RED41352) - The operator is now supported on [Openshift 4.4](https://docs.openshift.com/container-platform/4.4/welcome/index.html).

- DB controller resources via the OLM (RED41755) - Support for configuration of DB controller resources was added to the OLM (preview channel).

Important fixes

- Openshift OLM upgrade support was fixed. Also, installing past versions was added through dedicated channels. (RED44130)
- Fixed log_collector failures when pods were not scheduled. (RED45347)
- Fixed wrong handling of the operator environment variables. Specifically, enabling/disabling the database controller now works correctly. (RED45351)

Known limitations

- CrashLoopBackOff causes cluster recovery to be incomplete  (RED33713) - When a pod status is CrashLoopBackOff and we run the cluster recovery, the process will not complete. The solution is to delete the crashing pods manually and recovery process will continue.

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

- Cluster CR (REC) errors are not reported after invalid updates (RED25542) - 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 (RED32805) - When a cluster is in an unreachable state the state is still running instead of being reported as an error.

- Readiness probe incorrect on failures (RED39300) - STS Readiness probe doesn't mark a node as not ready when rladmin status on the node fails

- Role missing on replica sets (RED39002) - The redis-enterprise-operator role is missing permission on replica sets.

- Private registries are not supported on OpenShift 3.11 (RED38579) - Openshift 3.11 doesn't support dockerhub private registry. This is a known OpenShift issue.

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

- 5.4.10 negatively impacts 5.4.6 (RED37233) - K8S-based 5.4.10 clusters seem to negatively impact existing 5.4.6

- Node CPU usage is reported instead of pod CPU usage (RED36884) - In Kubernetes, the node CPU usage we report on is the usage of the K8S worker node hosting the REC pod.

- Clusters must be named "rec" in OLM-based deployments (RED39825) - 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) is bound to a specific service account name (i.e., "rec"). The workaround is to name the cluster "rec".

- Updating UI service in Rancher (RED45771) - Updating the UI service type may fail in Rancher. When this happens, delete the service manually and the operator will recreate it correctly.

- Master pod label in Rancher (RED42896) - Master pod is not always labeled in Rancher.

Deprecation notice

Support for Kubernetes version 1.11 and 1.12 is deprecated (excludes Openshift 3.11, which continues to be supported).

Compatibility updates

- Added support for Rancher
- Added support for Openshift 4.4


Redis Enterprise for Kubernetes Release Notes 6.0.6-24 (August 2020)

Summary: Various bug fixes.

Overview

The Redis Enterprise K8s 6.0.6-24 release is a *maintenance release* on top of [6.0.6-23](https://github.com/RedisLabs/redis-enterprise-k8s-docs/releases/tag/v6.0.6-23) providing support for the latest [Redis Enterprise Software release 6.0.6-39](https://docs.redislabs.com/latest/rs/release-notes/rs-6-0-may-2020/) and includes several bug fixes.

Overview

This release of the operator provides:

 * Various bug fixes

To upgrade your deployment to this latest release, see ["Upgrade a Redis Enterprise cluster (REC) on Kubernetes"]().

Images

* **Redis Enterprise** - redislabs/redis:6.0.6-39 or redislabs/redis:6.0.6-39.rhel7-openshift
 * **Operator** - redislabs/operator:6.0.6-24
 * **Services Rigger** - redislabs/k8s-controller:6.0.6-24 or redislabs/services-manager:6.0.6-24 (on the RedHat registry)

Important fixes

* A fix for database observability where after 24 hours after creation or update, the controller was unable to observe the database (RED46149)
 * A fix for a log collector crash on Windows when pods were not running (RED45477)

Known limitations

When a pod status is CrashLoopBackOff and we run the cluster recovery, the process will not complete. The workaround is to delete the crashing pods manually and recovery process will continue.

A cluster name longer than 20 characters will result in a rejected route configuration as the host part of the domain name exceeds 63 characters. The workaround is to limit cluster name to 20 characters or less.

A cluster CR specification error is not reported if two or more invalid CR resources are updated in sequence.

When a cluster is in an unreachable state the state is still running instead of being reported as an error.

STS Readiness probe doesn't mark a node as not ready when rladmin status on the node fails.

Role missing on replica sets (RED39002)

The redis-enterprise-operator role is missing permission on replica sets.

Openshift 3.11 doesn't support dockerhub private registry. This is a known OpenShift issue.

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.

Kubernetes-based 5.4.10 deployments seem to negatively impact existing 5.4.6 deployments that share a Kubernetes cluster.

In Kubernetes, the node CPU usage we report on is the usage of the Kubernetes worker node hosting the REC pod.

In OLM-deployed operators, the deployment of the cluster will fail if the name is not "rec". When the operator is deployed with the OLM, the security context constraints (scc) is bound to a specific service account name (i.e., "rec"). The workaround is to name the cluster "rec".

Updating UI service in Rancher (RED45771)

Updating the UI service type may fail in Rancher. When this happens, delete the service manually and the operator will recreate it correctly.

Master pod label in Rancher (RED42896)

Master pod is not always labeled in Rancher.

Deprecation notice

Support for K8s version 1.11 and 1.12 is deprecated (excludes Openshift 3.11, which continues to be supported). Openshift 4.1 and 4.2 are deprecated (already End Of Life by Red Hat).


Redis Enterprise for Kubernetes Release Notes 6.0.6-6 (June 2020)

Overview

Redis Enterprise for Kubernetes 6.0.6-6 is now available. This release includes Redis Enterprise (RS) version [6.0]() and introduces new features, improvements, and bug fixes.

Overview

This release of the operator provides:

- Support for the Redis Enterprise Software release 6.0.6
- Includes the new database and admission controllers
- Various improvements and bug fixes

To upgrade your deployment to this latest release, see ["Upgrade a Redis Enterprise cluster (REC) on Kubernetes"]().

If you are running Active-Active (CRBD) databases on a previous release, do not upgrade to 6.0.6-6 at this time. There is an issue with the upgrade process that is currently being investigated (RED43635). For more information and support please [contact Redis support](https://redislabs.com/company/support/).

Images

- **Redis Enterprise** - redislabs/redis:6.0.6-6 or redislabs/redis:6.0.6-6.rhel7-openshift
- **Operator** - redislabs/operator:6.0.6-6 or redislabs/operator:6.0.6-6.rhel7
- **Services Rigger** - redislabs/k8s-controller:6.0.6-6 or redislabs/k8s-controller:6.0.6-6.rhel7

New features and improvements

- Database controller - A new database controller in the operator provides the ability to create
and manage databases on a Redis Enterprise cluster via a custom resource (RED36516).

- Admission controller - A new admission controller in the operator provides validation of
database custom resources (RED36458).

- Pod tolerations - Support for specifying Redis Enterprise cluster node pod tolerations of node taints
has been added to the cluster CR (see podTolerations) (RED33069).

- Pod annotations - Support for specifying Redis Enterprise cluster node pod annotations has been
added to the cluster CR (see podAnnotations) (RED35613).

- Kubernetes versions - Support for Kubernetes 1.17 was added and versions 1.9 and 1.10 (previously deprecated) are no longer supported (RED41049).

- Improved OLM Experience - The overall user experience and documentation in the OLM (OperatorHub) has been improved (RED37008).

- Resource limits - Resource limits have been added to the recommended operator configuration (RED39572).

- LoadBalancer service type added - The `LoadBalancer` value has been added to the `databaseServiceType` option in `servicesRiggerSpec` (RED43215):

    [code example]

Important fixes

- Service creation failure causes cluster setup failure (RED37197)
- UI service update failure (RED37198)
- Error shown in OLM deployment: "The field status.state is invalid" (RED40278)
- OLM: StatefulSet not listed as an object owned by the Redis Enterprise Cluster (RED39296)
- Setting extraLabels in the cluster CR did not label pods on OpenShift (RED39763)
- log_collector failed to get the pods logs when a namespace wasn't given (RED39292)
- Role and RoleBinding created or updated using an existing ServiceAccount in REC spec (RED42912)

Known limitations

- CrashLoopBackOff pod status and cluster recovery - When a pod status is CrashLoopBackOff and we run the cluster recovery, the process
will not complete. The solution is to delete the crashing pods manually and
recovery process will continue (RED33713).

- Active-Active (CRDB) - limitation on cluster name length - A cluster name longer than 20 characters will result in a rejected route
configuration as the host part of the domain name exceeds 63 characters. Cluster
names must be limited to 20 characters or less (RED25871).

- Active-Active (CRDB) service broker cleanup - The service broker doesn't clean up database service bindings in case of failures.
These bindings must be removed manually (RED25825).

- Service broker deployment error - The service broker deployment results in an error when two types of service naming
schemes are set. Choosing one of the methods will resolve this error (`redis-port`
is the recommended default) (RED25547).

- Cluster spec invalid errors not reported - A cluster CR specification error is not reported if two or more invalid CR resources are
updated in sequence (RED25542).

- Unreachable cluster does not produce an error - When a cluster is in an unreachable state the state is still `running` instead of
being reported as an error (RED32805).

- Readiness probe ignores rladmin failure - STS Readiness probe doesn't mark a node as not ready when rladmin status nodes fails (RED39300).

- Missing permission for role - The redis-enterprise-operator role is missing permission on replicasets (RED39002).

- Openshift 3.11 doesn't support DockerHub private registry - Openshift 3.11 doesn't support DockerHub private registry. This is a known OpenShift
issue and not addressable by Redis Enterprise for Kubernetes (RED38579).

- Possible DNS conflicts within cluster nodes - DNS conflicts are possible between the cluster mdns_server and the K8s DNS.
This only impacts DNS resolution from within cluster node and while using the full fqdn *.cluster.local (RED37462).

- Coexistence of 5.4.10 and 5.4.6 clusters - K8s clusters with Redis Enterprise 5.4.6 clusters are negatively affected by installing a Redis Enterprise 5.4.10 cluster due to changes in CRD (CustomeResourceDefinition) (RED37233).

- Redis Enterprise CPU utilization metric reports at K8s node level rather than at pod level - In Kubernetes, the node CPU usage we report on is the usage of the K8S worker node hosting the REC pod (RED-36884). Pod resource utilization should be measured by K8s-native means rather than through the application.

- Cluster name is limited on OpenShift via OLM - 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)
is bound to a specific service account name (i.e., "rec"). Naming the cluster
"rec" resolves the issue (RED39825).

Coming Soon

The following lists features, fixes and changes the Redis team is currently investing in:

- Redis Enterprise and Kubernetes Container Artifacts - tarting from the next release of Redis Enterprise for K8s, new container artifacts will be published using different base images:

    - **Redis Enterprise** - A UBI (RHEL 7) base image will replace the Ubuntu and the RHEL7 base images
    - **Operator** - An Image built from scratch containing the Golang executable will replace the Ubuntu and the RHEL7 base images
    - **Services Rigger** - A UBI (RHEL 7) base image will replace the Ubuntu and the RHEL7 base images

- Deprecation notice - he service broker solution is deprecated and will not be supported starting from the next release of the Redis Enterprise Operator for Kubernetes.

- Additional Redis Enterprise Database configuration options in the Database Controller - We're currently investing in the following additional capabilities of the Database Controller:
    - Support for loading database modules
    - Support for setting up Alerts, expressed as K8s events
    - Support for configuring database backup options
    - Support for Kubernetes 1.18
    - Support for Rancher K8s distribution

servicesRiggerSpec:
       databaseServiceType: LoadBalancer