Overview

The Redis Enterprise K8s 6.2.10-34 supports the Redis Enterprise Software release 6.2.10 and includes feature improvements and bug fixes.

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

  **Do not** upgrade to this 6.2.10-34 release if you are an **OpenShift** customer and **also use modules**. Instead, **use the [6.2.10-45]()** release.

  There was a change in 6.2.10-34 to a new RHEL 8 base image for the Redis Server image. Due to binary differences in modules between the two operating systems, you cannot directly update RHEL 7 clusters to RHEL 8 when those clusters host databases using modules.

   Please contact support if you have further questions.

Images

This release includes the following container images:

* **Redis Enterprise**: `redislabs/redis:6.2.10-107` or  `redislabs/redis:6.2.10-107.rhel8-openshift`
* **Operator**: `redislabs/operator:6.2.10-34`
* **Services Rigger**: `redislabs/k8s-controller:6.2.10-34` or `redislabs/services-manager:6.2.10-34` (on the Red Hat registry)

New features

* Support database upgrade policy (major/latest) for REDB resources (RED-71028)
* Support for memcached type databases for REDB (RED-70284)(RED-75269)
* Use RHEL8 base images for OpenShift deployments (RED-72374)

Feature improvements

* OpenShift 4.10 support (RED-73966)
* Allow setting host time zone on running containers (RED-56810)
* AKS 1.23 support (RED-73965)
* EKS 1.22 support (RED-73972)

Fixed bugs

* Outdated SCC YAML file (RED-72026) (RED-73341)
* Admission container startup failure (RED-72081)
* Admission container restarts due to race condition with config map creation (RED-72268)
* Incorrect REDB status report during cluster recovery (RED-72944)
* Invalid REDB spec not always rejected by admission controller (RED-73145)

Compatibility notes

Below is a table showing supported distributions at the time of this release. See [Supported Kubernetes distributions]() for the current list of supported distributions.

| **Kubernetes version**  | **1.19**   | **1.20**   | **1.21**   | **1.22**   | **1.23**   |
|:------------------------|:----------:|:----------:|:----------:|:----------:|:----------:|
| Community Kubernetes    | deprecated | deprecated | supported  | supported  | supported* |
| Amazon EKS              | supported  | supported  | supported  |            |            |
| Azure AKS               |            |            | supported  | supported  | supported* |
| Google GKE              | supported  | supported  | supported  | supported  |            |
| Rancher 2.6             | supported  | supported  | supported  | supported  |            |
| **OpenShift version**   | **4.6**    | **4.7**    | **4.8**    | **4.9**    | **4.10**   |
|                         | deprecated | deprecated | supported  | supported  | supported* |
| **VMware TKGI version** | **1.10**   | **1.11**   | **1.12**   | **1.13**   |            |
|                         | supported  | supported  | supported* |            |            |

\* Support added in most recent release

Now supported

* OpenShift 4.10 is now supported
* kOps (Community Kubernetes) 1.23 is now supported
* AKS 1.23 is now supported
* EKS 1.22 is now supported

Deprecated

* OpenShift 4.6-4.7 is deprecated
* kOps (Community Kubernetes) 1.18-1.20 are deprecated
* GKE 1.19 is deprecated
* Rancher 2.6 - K8s 1.18 is deprecated
* AKS 1.20-1.21 are deprecated
* EKS 1.18-1.19 are deprecated

No longer supported

* Rancher version 2.5 (previously deprecated) is no longer supported (not supported by SUSE)
* OpenShift version 3.11 (previously deprecated) is no longer supported.

Known limitations

Large clusters

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

* **Warning** Openshift customers using modules cannot use 6.2.10-34 version

  **Do not** upgrade to this 6.2.10-34 release if you are an **OpenShift** customer and **also use modules**.

  There was a change in 6.2.10-34 to a new RHEL 8 base image for the Redis Server image. Due to binary differences in modules between the two operating systems, you cannot directly update RHEL 7 clusters to RHEL 8 when those clusters host databases using modules.

  This message will be updated as remediation plans and new steps are available to address this situation. Please contact support if you have further questions.

* 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 will exceed 63 characters. The workaround is to limit cluster name to 20 characters or less.

* Cluster CR (REC) errors are not reported after invalid updates (RED-25542)

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

* An unreachable cluster has status running (RED-32805)

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

* Readiness probe incorrect on failures (RED-39300)

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

* Role missing on replica sets (RED-39002)

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

* Internal DNS and Kubernetes DNS may have conflicts (RED-37462)

  DNS conflicts are possible between the cluster `mdns_server` and the K8s DNS. This only impacts DNS resolution from within cluster nodes for Kubernetes DNS names.

* 5.4.10 negatively impacts 5.4.6 (RED-37233)

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

* Node CPU usage is reported instead of pod CPU usage (RED-36884)

  In Kubernetes, the 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 (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 (i.e., "rec"). The workaround is to name the cluster "rec".

* REC clusters fail to start on Kubernetes clusters with unsynchronized clocks (RED-47254)

  When REC clusters are deployed on Kubernetes clusters with unsynchronized clocks, the REC cluster does not start correctly. The fix is to use NTP to synchronize the underlying K8s nodes.

* Deleting an OpenShift project with an REC deployed may hang (RED-47192)

  When 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 (RED-51921)

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

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

  There is no workaround at this time.

* REC might report error states on initial startup (RED-61707)

  There is no workaround at this time except to ignore the errors.

* PVC size issues when using decimal value in spec (RED-62132)

  The workaround for this issue is to make sure you use integer values for the PVC size.

* Following old revision of quick start guide causes issues creating an REDB due to unrecognized memory field name (RED-69515)

The workaround is to use the newer (current) revision of the quick start document available online.

* `autoUpgrade` set to true by operator might cause unexpected bdb upgrades when `redisUpgradePolicy` is set to true (RED-72351)

  Contact support if your deployment is impacted.

* Procedure to update credentials might be problematic on OpenShift when accessing the cluster externally using routes (RS issue)(RED-73251)(RED-75329)
  To workaround this, access the API from within the K8s cluster.


Redis Enterprise for Kubernetes Release Notes 6.2.10-4 (March 2022)

Summary: Added support for RS 6.2.10 as well as feature improvements and bug fixes.

Overview

The Redis Enterprise K8s 6.2.10-4 supports the Redis Enterprise Software release 6.2.10 and includes feature improvements and bug fixes.

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

Images

This release includes the following container images:

* **Redis Enterprise**: `redislabs/redis:6.2.10-90` or  `redislabs/redis:6.2.10-90.rhel7-openshift`
* **Operator**: `redislabs/operator:6.2.10-4`
* **Services Rigger**: `redislabs/k8s-controller:6.2.10-4` or `redislabs/services-manager:6.2.10-4` (on the Red Hat registry)

Feature improvements

* REDB status - bundled Redis versions for cluster shown in status (RED-44074)
* OLM (OperatorHub) - example REC contains image references to Red Hat servers (RED-44439)
* REDB status - added information about database backups (RED-45577)
* Added dedicated metrics exporter service (service name ending in -prom). Using the service is recommended for gathering Prometheus data about the cluster. Using the service with the UI service is not recommended (RED-61807)
* REDB - added support for shard_placement
* RS 6.2.10 support (RED-69142)
* REDB - control autoUpgrade (RED-71157)

Fixed bugs

* Cluster no longer refuses wrong sized volume to create clusters (error shown instead) (RED-61284)

* Resolved high CPU usage when many pods are running within the namespace (RED-69682)

* TKGI - support 1.11/1.12 (RED-70579)

* Fixed rack awareness label in documentation (RED-70622)

* Fixed crash in admission container when admission service is missing (RED-70678)

* Services rigger deployment generation no longer increases without changes (RED-70835)

Known limitations

Large clusters

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

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 will exceed 63 characters. The workaround is to limit cluster name to 20 characters or less.

Cluster CR (REC) errors are not reported after invalid updates (RED-25542)

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

An unreachable cluster has status running (RED-32805)

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

Readiness probe incorrect on failures (RED-39300)

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

Role missing on replica sets (RED-39002)

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

Private registries are not supported on OpenShift 3.11 (RED-38579)

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

Internal DNS and Kubernetes DNS may have conflicts (RED-37462)

DNS conflicts are possible between the cluster `mdns_server` and the K8s DNS. This only impacts DNS resolution from within cluster nodes for Kubernetes DNS names.

5.4.10 negatively impacts 5.4.6 (RED-37233)

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

Node CPU usage is reported instead of pod CPU usage (RED-36884)

In Kubernetes, the 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 (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 (i.e., "rec"). The workaround is to name the cluster "rec".

REC clusters fail to start on Kubernetes clusters with unsynchronized clocks (RED-47254)

When REC clusters are deployed on Kubernetes clusters with unsynchronized clocks, the REC cluster does not start correctly. The fix is to use NTP to synchronize the underlying K8s nodes.

Deleting an OpenShift project with an REC deployed may hang (RED-47192)

When 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 (RED-51921)

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

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

There is no workaround at this time.

REC might report error states on initial startup (RED-61707)

There is no workaround at this time except to ignore the errors.

PVC size issues when using decimal value in spec (RED-62132)

The workaround for this issue is to make sure you use integer values for the PVC size.

Following old revision of quick start guide causes issues creating an REDB due to unrecognized memory field name (RED-69515)

The workaround is to use the newer (current) revision of the quick start document available online.

`autoUpgrade` set to true by operator might cause unexpected bdb upgrades when `redisUpgradePolicy` is set to true (RED-72351)

Contact support if your deployment is impacted.

Compatibility Notes

See [Supported Kubernetes distributions]() for the full list of supported distributions.

Now supported

* TKGI 1.11 (K8s 1.20) is supported
* Rancher version 2.6 is supported

Deprecated

* Rancher version 2.5 support is deprecated

No longer supported

* Rancher version 2.5 / K8s 1.17 (previously deprecated) is no longer supported (not supported by SUSE)


Redis Enterprise for Kubernetes release notes 6.2.10-45 (July 2022)

Summary: Support added for additional distributions as well as some feature improvements.

Overview

The Redis Enterprise K8s 6.2.10-45 supports the Redis Enterprise Software release 6.2.10 and includes feature improvements and bug fixes.

The key bug fixes and known limitations are described below.

Images

This release includes the following container images:

* **Redis Enterprise**: `redislabs/redis:6.2.10-129` or  `redislabs/redis:6.2.10-129.rhel8-openshift` (or `redislabs/redis:6.2.10-129.rhel7-openshift` if upgrading from a RHEL7 cluster)
* **Operator**: `redislabs/operator:6.2.10-45`
* **Services Rigger**: `redislabs/k8s-controller:6.2.10-45` or `redislabs/services-manager:6.2.10-45` (on the Red Hat registry)

Feature improvements

* OpenShift OperatorLifecycleManager support on restricted networks (RED-72968)
* `log_collector` script uses `oc` command with automatic detection of OpenShift (RED-73215)
* Operator uses `policy/v1` for `PodDisruptionBudget`(RED-78564)
* Added support for Kubernetes distributions (see Compatibility notes below)

Fixed bugs

* Upgrade failures when RHEL7 was used (RED-77890)
* Log collector failures when Python2 was used (RED-73403)

API changes

The `digestHash` optional field added to `imageSpec` fields in the REC. This field should be used in disconnected environments using the OperatorLifecycleManager.

Compatibility notes

Below is a table showing supported distributions at the time of this release. See [Supported Kubernetes distributions]() for the current list of supported distributions.

| **Kubernetes version**  | 1.19       | 1.20       | 1.21       | 1.22       | 1.23       | 1.24       |
|:------------------------|:----------:|:----------:|:----------:|:----------:|:----------:|:----------:|
| Community Kubernetes    |            |            | deprecated | supported  | supported  | supported* |
| Amazon EKS              | deprecated | deprecated | supported  | supported* |            |
| Azure AKS               |            |            | deprecated | supported  | supported  |
| Google GKE              | deprecated | deprecated | supported  | supported  |supported*  |
| Rancher 2.6             | deprecated | deprecated | supported  | supported  |            |
| **OpenShift version**   | **4.6**    | **4.7**    | **4.8**    | **4.9**    | **4.10**   |
|                         |            | deprecated | deprecated | supported  | supported  |
| **VMware TKGI version** | **1.10**   | **1.11**   | **1.12**   | **1.13**   |            |
|                         | deprecated | deprecated | supported* | supported* |            |

\* Support added in this release

Support added

* K8s community version 1.24

Deprecated

* OpenShift 4.7-4.8
* Kubernetes 1.20
* Rancher 2.6 for K8s 1.19-1.20
* TKGI 1.10-11

No longer supported

* OpenShift 4.6 (previously deprecated)
* Kubernetes 1.18-1.19 (previously deprecated)
* Rancher 2.6 for K8s 1.18 (previously deprecated)
* AKS 1.20-1.21 (previously deprecated)
* EKS 1.18-1.19 (previously deprecated)
* GKE 1.19 (previously deprecated)

Known limitations

Large clusters

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

* 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 will exceed 63 characters. The workaround is to limit cluster name to 20 characters or less.

* Cluster CR (REC) errors are not reported after invalid updates (RED-25542)

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

* An unreachable cluster has status running (RED-32805)

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

* Readiness probe incorrect on failures (RED-39300)

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

* Role missing on replica sets (RED-39002)

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

* Private registries are not supported on OpenShift 3.11 (RED-38579)

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

* Internal DNS and Kubernetes DNS may have conflicts (RED-37462)

  DNS conflicts are possible between the cluster `mdns_server` and the K8s DNS. This only impacts DNS resolution from within cluster nodes for Kubernetes DNS names.

* 5.4.10 negatively impacts 5.4.6 (RED-37233)

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

* Node CPU usage is reported instead of pod CPU usage (RED-36884)

  In Kubernetes, the 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 (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 (i.e., "rec"). The workaround is to name the cluster "rec".

* REC clusters fail to start on Kubernetes clusters with unsynchronized clocks (RED-47254)

  When REC clusters are deployed on Kubernetes clusters with unsynchronized clocks, the REC cluster does not start correctly. The fix is to use NTP to synchronize the underlying K8s nodes.

* Deleting an OpenShift project with an REC deployed may hang (RED-47192)

  When 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 (RED-51921)

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

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

  There is no workaround at this time.

* REC might report error states on initial startup (RED-61707)

  There is no workaround at this time except to ignore the errors.

* PVC size issues when using decimal value in spec (RED-62132)

  The workaround for this issue is to make sure you use integer values for the PVC size.

* Following old revision of quick start guide causes issues creating an REDB due to unrecognized memory field name (RED-69515)

The workaround is to use the newer (current) revision of the quick start document available online.

* `autoUpgrade` set to true by operator might cause unexpected bdb upgrades when `redisUpgradePolicy` is set to true (RED-72351)

  Contact support if your deployment is impacted.

* Procedure to update credentials might be problematic on OpenShift when accessing the cluster externally using routes (RS issue)(RED-73251)(RED-75329)
  To workaround this, access the API from within the K8s cluster.


Redis Enterprise for Kubernetes release notes 6.2.12-1 (Sept 2022)

Summary: Support added for additional distributions, as well as feature improvements and bug fixes.

Overview

The Redis Enterprise K8s 6.2.12-1 supports the Redis Enterprise Software release 6.2.12 and includes feature improvements and bug fixes.

The key bug fixes and known limitations are described below.

Images

This release includes the following container images:

* **Redis Enterprise**: `redislabs/redis:6.2.12-82` or  `redislabs/redis:6.2.12-82.rhel8-openshift`
* **Operator**: `redislabs/operator:6.2.12-1`
* **Services Rigger**: `redislabs/k8s-controller:6.2.12-1` or `redislabs/services-manager:6.2.12-1` (on the Red Hat registry)

Feature improvements

* Redis Enterprise Software 6.2.12 support (RED-83829)
* Added support for annotations on services created by Redis Enterprise (RED-56245)
* Support for additional builds of same Redis Software version with same operator version. The list of supported builds will be published. (RED-78757)

Bug fixes

* Fixed Golang related vulnerabilities (RED-79205)
* Log collector creating larger packages (RED-79650)
* Log collector crashes when Redis Enterprise cluster is not running (RED-79996)
* Redis Enterprise Software pods termination process could lead, in some circumstances, to pod shutdown without proper failover of its master shards. This has been fixed so that the failover attempts are retried indefinitely within the grace period, which by default is 1 year. The grace period is controllable via the redisEnterpriseTerminationGracePeriodSeconds parameter in the REC (but note that shutting down a pod without the proper failovers may lead to data loss).(RED-75388)

API changes

The Redis Enterprise cluster `podSecurityPolicy` is deprecated. This is still supported but will be removed when all K8s versions supporting the feature are removed.

Compatibility notes

Below is a table showing supported distributions at the time of this release. See [Supported Kubernetes distributions]() for the current list of supported distributions.

| **Kubernetes version**  | 1.20       | 1.21       | 1.22       | 1.23       | 1.24       |
|:------------------------|:----------:|:----------:|:----------:|:----------:|:----------:|
 | Community Kubernetes   |            |            | supported  | supported  | supported |
| Amazon EKS              |            | deprecated | supported  | supported* |
| Azure AKS               |            |            | supported  | supported  | supported* |
| Google GKE              |            | deprecated | supported  | supported  | supported* |
| Rancher 2.6             |            | supported  | supported  | supported* |            |
| **OpenShift version**   | **4.7**    | **4.8**    | **4.9**    | **4.10**   | **4.11**   |
|                         | deprecated | deprecated | supported  | supported  | supported* |
| **VMware TKGI version** | **1.11**   | **1.12**   | **1.13**   | **1.14**   | **1.15**   |
|                         | deprecated | deprecated | supported* | supported* |            |

\* Support added in this release

Support added

* Azure AKS 1.24
* Amazon EKS 1.23
* Google GKE 1.24
* OpenShift 4.11
* Rancher 1.23
* VMware TKGI 1.14

Deprecated

* Amazon EKS 1.21
* Google GKE 1.21
* OpenShift 4.7
* OpenShift 4.8
* VMware TKGI 1.11
* VMware TKGI 1.12

No longer supported

* Community Kubernetes 1.21
* Amazon EKS 1.19, 1.20
* Azure AKS 1.21
* Google GKE 1.19, 1.20
* Rancher 2.6 1.19, 1.20
* VMware TKGI 1.10

Before upgrading

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

Supported upgrade paths

If you are using operator version 6.2.8-15 or earlier, you cannot upgrade directly to operator versions 6.2.12 through 6.4.2-5. You must upgrade to operator version 6.2.10-45 before you can upgrade to operator versions between 6.2.12 and 6.4.2-5. However, upgrades directly to operator version 6.4.2-6 are supported.

Known limitations

Large clusters

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

* 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 will exceed 63 characters. The workaround is to limit cluster name to 20 characters or less.

* Cluster CR (REC) errors are not reported after invalid updates (RED-25542)

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

* An unreachable cluster has status running (RED-32805)

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

* Readiness probe incorrect on failures (RED-39300)

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

* Role missing on replica sets (RED-39002)

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

* Private registries are not supported on OpenShift 3.11 (RED-38579)

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

* Internal DNS and Kubernetes DNS may have conflicts (RED-37462)

  DNS conflicts are possible between the cluster `mdns_server` and the K8s DNS. This only impacts DNS resolution from within cluster nodes for Kubernetes DNS names.

* 5.4.10 negatively impacts 5.4.6 (RED-37233)

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

* Node CPU usage is reported instead of pod CPU usage (RED-36884)

  In Kubernetes, the 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 (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 (i.e., "rec"). The workaround is to name the cluster "rec".

* REC clusters fail to start on Kubernetes clusters with unsynchronized clocks (RED-47254)

  When REC clusters are deployed on Kubernetes clusters with unsynchronized clocks, the REC cluster does not start correctly. The fix is to use NTP to synchronize the underlying K8s nodes.

* Deleting an OpenShift project with an REC deployed may hang (RED-47192)

  When 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 (RED-51921)

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

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

  There is no workaround at this time.

* REC might report error states on initial startup (RED-61707)

  There is no workaround at this time except to ignore the errors.

* PVC size issues when using decimal value in spec (RED-62132)

  The workaround for this issue is to make sure you use integer values for the PVC size.

* Following old revision of quick start guide causes issues creating an REDB due to unrecognized memory field name (RED-69515)

  The workaround is to use the newer (current) revision of the quick start document available online.

* `autoUpgrade` set to true by operator might cause unexpected bdb upgrades when `redisUpgradePolicy` is set to true (RED-72351)

  Contact support if your deployment is impacted.

* Procedure to update credentials might be problematic on OpenShift when accessing the cluster externally using routes (RS issue)(RED-73251)(RED-75329)
  To workaround this, access the API from within the K8s cluster.

* On Windows, `log_collector` doesn't recognize the namespace given with the `-n` flag (RED-83532)

  To workaround this, use a different operating system.

* Active-Active database creation will fail if the ingress class annotation is not exactly "nginx" when using Nginx ingress controller (RED-83070)


Redis Enterprise for Kubernetes release notes 6.2.18-3 (Nov 2022)

Overview

The Redis Enterprise K8s 6.2.18-3 supports the Redis Enterprise Software release 6.2.18 and includes feature improvements and bug fixes.

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

If you use NGINX as an ingress controller for Redis Enterprise, **do not upgrade** to the 6.2.18-3 release. Skip this release and upgrade to version [6.2.18-41]() instead.

Images

This release includes the following container images:

* **Redis Enterprise**: `redislabs/redis:6.2.18-58` or  `redislabs/redis:6.2.18-58.rhel8-openshift` (or `redislabs/redis:6.2.18-58.rhel7-openshift` if upgrading from RHEL 7)
* **Operator**: `redislabs/operator:6.2.18-3`
* **Services Rigger**: `redislabs/k8s-controller:6.2.18-3` or `redislabs/services-manager:6.2.18-3` (on the Red Hat registry)

New features

* Support for [Redis Flex]() (RED-78613)

Feature improvements

* The `podSecurityPolicyName` field in `RedisEnterpriseCluster` resources is now deprecated for Kubernetes versions 1.24 or earlier, and invalid for 1.25 and later. Customers are advised to switch to using the [`PodSecurityAdmission`](https://kubernetes.io/docs/concepts/security/pod-security-admission/) or alternative methods to enforce pod security (RED-81921).

* Added support for VMware [Tanzu Kubernetes Grid (TKG)](https://docs.vmware.com/en/VMware-Tanzu-Kubernetes-Grid/index.html), in addition to [Tanzu Kubernetes Grid Integration Edition (TKGI)](https://docs.vmware.com/en/VMware-Tanzu-Kubernetes-Grid-Integrated-Edition/index.html) that was previously and is still supported (RED-65630).

* Added support for PEM encryption through the [Redis Enterprise cluster API]()(RED-78613).

* Hardened security context constraints to align with standards for OpenShift 4.11 (RED-83215).

* Changed log collector default to avoid collection of non-Redis Enterprise logs and items (RED-83216).

* Allowed configuration of the Redis Enterprise cluster (REC) service type (RED-84644).

Bug fixes

* Allow any ingress class name annotation when using NGINX ingress controller. This is no longer required to be exactly `nginx` (RED-79205).
* Fixed log collector handling of namespace parameter on Windows (RED-83532).
* Fixed issue with updating credentials on Openshift when accessing the cluster externally with routes (RED-73251, RED-75329).

API changes

The following fields were added to the [Redis Enterprise cluster (REC) API]():

* Added `.services.apiService.type` to allow configuration of the API service type.
* Made `.redisOnFlashSpec` available by default.
* Made `.ocspConfiguration` available by default for configuring OCSP stapling.
* Made `.encryptPkeys` available by default for configuring PEM encryption.

The following fields were added to the [Redis Enterprise database (REDB) API]():

* `.isRoF` and `.rofRamSize` added to support the [Redis Flex feature]().

Compatibility notes

Below is a table showing supported distributions at the time of this release. See [Supported Kubernetes distributions]() for the current list of supported distributions.

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

\* Support added in this release

Before upgrading

Supported upgrade paths

OpenShift versions 6.2.12 or earlier

Due to a change in the SCC, on OpenShift clusters running version 6.2.12 or earlier upgrading to version 6.2.18 or later, where `node:1` is <b>not</b> the master node, the upgrade might get stuck.

For more info and steps to prevent this issue, see [upgrade a Redis Enterprise cluster (REC)]().

Operator version 6.4.2-6 includes a fix for this issue.

Large clusters

Known limitations

Large clusters

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

* 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 will exceed 63 characters. The workaround is to limit cluster name to 20 characters or less.

* Cluster CR (REC) errors are not reported after invalid updates (RED-25542)

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

* An unreachable cluster has status running (RED-32805)

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

* Readiness probe incorrect on failures (RED-39300)

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

* Internal DNS and Kubernetes DNS may have conflicts (RED-37462)

  DNS conflicts are possible between the cluster `mdns_server` and the K8s DNS. This only impacts DNS resolution from within cluster nodes for Kubernetes DNS names.

* 5.4.10 negatively impacts 5.4.6 (RED-37233)

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

* Node CPU usage is reported instead of pod CPU usage (RED-36884)

  In Kubernetes, the 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 (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 (i.e., "rec"). The workaround is to name the cluster "rec".

* REC clusters fail to start on Kubernetes clusters with unsynchronized clocks (RED-47254)

  When REC clusters are deployed on Kubernetes clusters with unsynchronized clocks, the REC cluster does not start correctly. The fix is to use NTP to synchronize the underlying K8s nodes.

* Deleting an OpenShift project with an REC deployed may hang (RED-47192)

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

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

  There is no workaround at this time.

* REC might report error states on initial startup (RED-61707)

  There is no workaround at this time except to ignore the errors.

* PVC size issues when using decimal value in spec (RED-62132)

  The workaround for this issue is to make sure you use integer values for the PVC size.

* Following old revision of quick start guide causes issues creating an REDB due to unrecognized memory field name (RED-69515)

  The workaround is to use the newer (current) revision of the quick start document available online.

* `autoUpgrade` set to true by operator might cause unexpected bdb upgrades when `redisUpgradePolicy` is set to true (RED-72351)

  Contact support if your deployment is impacted.

Security

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


Redis Enterprise for Kubernetes release notes 6.2.18-41 (Dec 2022)

Summary: This is a maintenance release for 6.2.18 and includes bug fixes.

Overview

The Redis Enterprise K8s 6.2.18-41 is a maintenance release which supports the Redis Enterprise Software release 6.2.18 and contains bug fixes.

The key bug fixes and known limitations are described below.

 Due to a change in the SCC, on OpenShift clusters running version 6.2.12 or earlier upgrading to version 6.2.18 or later, where `node:1` is <b>not</b> the master node, the upgrade might get stuck.

For more info and steps to prevent this issue, see [upgrade a Redis Enterprise cluster (REC)]().

Images

* **Redis Enterprise**: `redislabs/redis:6.2.18-65`
* **Operator**: `redislabs/operator:6.2.18-41`
* **Services Rigger**: `redislabs/k8s-controller:6.2.18-41`

OpenShift images

**OLM operator version**: `v6.2.18-41a`

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

Bug fixes

* Fixed issues with incorrect image digest (OLM/OpenShift) (RED-88863)
* Fixed upgrade issue for using NGINX-based ingress with Active-Active databases. (RED-88882)
* Upgraded to Redis Software 6.2.18-65 (RED-88985)
* Fixed upgrade issue with OLM (RED-89170)
* Removed non-core Python dependencies from the log collector (RED-90108)
* Fixed issues with running log collector on OLM (RED-90129

Compatibility notes

Below is a table showing supported distributions at the time of this release. See [Supported Kubernetes distributions]() for the current list of supported distributions.

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

\* Support added in this release

Before upgrading

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

 ### Supported upgrade paths

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

Known limitations

Large clusters

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

* 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 will exceed 63 characters. The workaround is to limit cluster name to 20 characters or less.

* Cluster CR (REC) errors are not reported after invalid updates (RED-25542)

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

* An unreachable cluster has status running (RED-32805)

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

* Readiness probe incorrect on failures (RED-39300)

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

* Internal DNS and Kubernetes DNS may have conflicts (RED-37462)

  DNS conflicts are possible between the cluster `mdns_server` and the K8s DNS. This only impacts DNS resolution from within cluster nodes for Kubernetes DNS names.

* 5.4.10 negatively impacts 5.4.6 (RED-37233)

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

* Node CPU usage is reported instead of pod CPU usage (RED-36884)

  In Kubernetes, the 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 (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 (i.e., "rec"). The workaround is to name the cluster "rec".

* REC clusters fail to start on Kubernetes clusters with unsynchronized clocks (RED-47254)

  When REC clusters are deployed on Kubernetes clusters with unsynchronized clocks, the REC cluster does not start correctly. The fix is to use NTP to synchronize the underlying K8s nodes.

* Deleting an OpenShift project with an REC deployed may hang (RED-47192)

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

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

  There is no workaround at this time.

* REC might report error states on initial startup (RED-61707)

  There is no workaround at this time except to ignore the errors.

* PVC size issues when using decimal value in spec (RED-62132)

  The workaround for this issue is to make sure you use integer values for the PVC size.

* Following old revision of quick start guide causes issues creating an REDB due to unrecognized memory field name (RED-69515)

  The workaround is to use the newer (current) revision of the [quick start document]() available online.

* `autoUpgrade` set to true by operator might cause unexpected bdb upgrades when `redisUpgradePolicy` is set to true (RED-72351)

  Contact support if your deployment is impacted.

Security

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


Redis Enterprise for Kubernetes release notes 6.2.18-41 (Jan 2023)

Summary: This is a maintenance release for 6.2.18 and includes support for Redis Enterprise 6.2.18-72.

Overview

This is a maintenance release of Redis Enterprise for Kubernetes 6.2.18-41 that adds supports for Redis Enterprise 6.2.18-72.

New images and fixes are listed below. Refer to [6.2.18-41 (Dec 2022]() for compatibility notes and known limitations.

 Due to a change in the SCC, on OpenShift clusters running version 6.2.12 or earlier upgrading to version 6.2.18 or later, where `node:1` is <b>not</b> the master node, the upgrade might get stuck.

For more info and steps to prevent this issue, see [upgrade a Redis Enterprise cluster (REC)]().

Images

DockerHub images are available at `docker.io/`.

* **Redis Enterprise**: `redislabs/redis:6.2.18-72`
* **Operator**: `redislabs/operator:6.2.18-41`
* **Services Rigger**: `redislabs/k8s-controller:6.2.18-41`

OpenShift images

**OLM operator version**: `v6.2.18-41c`

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

Feature enhancements

* Upgraded to support Redis Enterprise 6.2.18-72

Compatibility notes

See [Redis Enterprise for Kubernetes release notes 6.2.18-41 (Dec 2022)]().

Before upgrading

Known limitations

Security

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


Redis Enterprise for Kubernetes Release Notes 6.2.4-1 (September 2021)

Summary: Support for RS 6.2.4 and OpenShift 4.8. Support for K8s 1.19 (EKS and AKS), K8s 1.20 (Rancher, EKS, AKS), K8s 1.21 (GKE and kOps).

Overview

The Redis Enterprise [K8s 6.2.4-1](https://github.com/RedisLabs/redis-enterprise-k8s-docs/releases/tag/v6.2.4-1) release provides support for the [Redis Enterprise Software release 6.2.4]() and includes several enhancements and bug fixes.

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

Images

This release includes the following container images:

* **Redis Enterprise**: `redislabs/redis:6.2.4-55` or  `redislabs/redis:6.2.4-55.rhel7-openshift`
* **Operator**: `redislabs/operator:6.2.4-1`
* **Services Rigger**: `redislabs/k8s-controller:6.2.4-1` or `redislabs/services-manager:6.2.4-1` (on the Red Hat registry)

New features

* Internode encryption configuration through K8s custom resources (RED-59699, RED-60318)

Feature improvements

* Support for addition attribute in REDB secret containing comma separated list of service names (RED-48469)
* Support OpenShift 4.8 (K8s 1.21) (RED-59424)
* Support K8s 1.21 - GKE (RED-59048)
* Support K8s 1.21 - kOps (RED-59047)
* Support K8s 1.19-1.21 - EKS (RED-60287)
* Support K8s 1.19, 1.20 - AKS (RED-59050)
* Support K8s 1.20 - Rancher (RED-59049)

Fixed bugs

* Fixed issue with RS pods not recovering from container failures (RED-53042)
* Fixed rare problem of Redis Enterprise pod restarting too early while statefulSet was rolling out, causing quorum loss (RED-53042)
* Improved Github public documentation around using the admission controller with multiple namespaces (RED-59915)
* Fixed integration issues with HashiCorp Vault enterprise namespaces and custom auth paths (RED-61273)

Known limitations

Large clusters

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

Applying bundle.yaml generated a warning

When applying bundle.yaml on K8s clusters 1.20 and above, the following warning is generated:
[code example]
The warning can be safely ignored. A future release will leverage the updated API version for CustomResourceDefinition, once support for K8s 1.22 is introduced.

Enabling the Kubernetes webhook generates a warning

When [installing](https://github.com/RedisLabs/redis-enterprise-k8s-docs#installation) and configuring the admission controller webhook (step 5), the following warning is generated:
[code example]
The warning can be safely ignored. A future release will leverage the updated API version for ValidatingWebhookConfiguration, once support for K8s 1.22 is introduced.

There is no workaround at this time

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 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 (RED-25542)

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

An unreachable cluster has status running (RED-32805)

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

Readiness probe incorrect on failures (RED-39300)

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

Role missing on replica sets (RED-39002)

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

Private registries are not supported on OpenShift 3.11 (RED-38579)

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

Internal DNS and Kubernetes DNS may have conflicts (RED-37462)

DNS conflicts are possible between the cluster `mdns_server` and the K8s DNS. This only impacts DNS resolution from within cluster nodes for Kubernetes DNS names.

5.4.10 negatively impacts 5.4.6 (RED-37233)

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

Node CPU usage is reported instead of pod CPU usage (RED-36884)

In Kubernetes, the 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 (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 (i.e., "rec"). The workaround is to name the cluster "rec".

REC clusters fail to start on Kubernetes clusters with unsynchronized clocks (RED-47254)

When REC clusters are deployed on Kubernetes clusters with unsynchronized clocks, the REC cluster does not start correctly. The fix is to use NTP to synchronize the underlying K8s nodes.

Deleting an OpenShift project with an REC deployed may hang (RED-47192)

When 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 (RED-51921)

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.

REC might report error states on initial startup (RED-61707)

There is no workaround at this time except to ignore the errors.

PVC size issues when using decimal value in spec (RED-62132)

The workaround for this issue is to make sure you use integer values for the PVC size.

Long REC names or namespace names cause failures (RED-62222)

The combined length of the REC name and namespace name must be equal to or less than 45 characters.

Compatibility Notes

See [Supported Kubernetes distributions]() for the full list of supported distributions.

Now supported

* OpenShift 4.8
* GKE K8s version 1.21
* kOps K8s version 1.21
* EKS K8s versions 1.19-1.21
* AKS K8s versions 1.19-1.20
* Rancher K8s version 1.20

No longer supported

* GKE K8s version 1.17 (previously deprecated)
* kOps K8s version 1.15 (previously deprecated)

Deprecation notice

* kOps 1.16 and 1.17 are deprecated
* VMWare TKGI 1.7 (K8s 1.16), VMWare TKGI 1.8 (K8s 1.17) are deprecated (no longer supported by VMWare)
* Openshift 3.11 (K8s 1.11) is now deprecated. Redis will continue to support existing deployments for the lifetime of Openshift 3.11, but new deployments are strongly discouraged.

Warning: apiextensions.k8s.io/v1beta1 CustomResourceDefinition is deprecated in v1.16+, unavailable in v1.22+; use apiextensions.k8s.io/v1 CustomResourceDefinition

Warning: admissionregistration.k8s.io/v1beta1 ValidatingWebhookConfiguration is deprecated in v1.16+, unavailable in v1.22+; use admissionregistration.k8s.io/v1 ValidatingWebhookConfiguration


Redis Enterprise for Kubernetes Release Notes 6.2.8-11 (January 2022)

Summary: Support for Istio as ingress controller, K8s 1.22 (AKS, kOps, GKE), OpenShift 4.9

Overview

The Redis Enterprise K8s 6.2.8-11 release provides support for the [Redis Enterprise Software release 6.2.8]() and includes several enhancements and bug fixes.

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

Images

This release includes the following container images:

* **Redis Enterprise**: `redislabs/redis:6.2.8-53` or  `redislabs/redis:6.2.8-53.rhel7-openshift`
* **Operator**: `redislabs/operator:6.2.8-11`
* **Services Rigger**: `redislabs/k8s-controller:6.2.8-11` or `redislabs/services-manager:6.2.8-11` (on the Red Hat registry)

Feature improvements

* Istio gateway/virtual services are supported as ingress controllers. Note that for Active-Active databases, the operator doesn't create ingress rules, and those should be manually configured. The version of Istio that was tested is Istio 1.12.0  (RED-64020)
* Support for K8s 1.22 (AKS, kOps, GKE) and OpenShift 4.9 (RED-64016)
* Support for pod termination grace period customization in the REC (advanced use case) (RED-67217)
* Improved security granularity of SCC configuration steps in documentation (RED-67321)
* Changed behavior when two databases with the same name are created on the cluster. The operator avoids creating a service for them to prevent possible corruption (RED-64535)
* Improved documentation about changing cluster credentials when using Hashicorp Vault (RED-65304)

Fixed bugs

* Upgraded Go dependencies marked as vulnerable (RED-63858, RED-68651)
* Avoided flooding operator logs with deprecation notices on K8s 1.21 (RED-67544)
* Fixed log collector utility issues running on Microsoft Windows (RED-67682)
* Fixed excessive updates to the RS cluster when using Windows line endings for TLS certificates (RED-67874)

Known limitations

Large clusters

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

Upgrading with the bundle using `kubectl apply -f` fails (RED-69515)

Upgrading with the bundle using `kubectl apply -f` fails, giving the following error:

`The CustomResourceDefinition "redisenterpriseclusters.app.redislabs.com" is invalid: spec.preserveUnknownFields: Invalid value: true: must be false in order to use defaults in the schema`

Workaround: Before the upgrade, set the 'spec.preserveUnknownFields` value to false on the REC custom resource. You can use the following command:

[code example]

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 will exceed 63 characters. The workaround is to limit cluster name to 20 characters or less.

Cluster CR (REC) errors are not reported after invalid updates (RED-25542)

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

An unreachable cluster has status running (RED-32805)

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

Readiness probe incorrect on failures (RED-39300)

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

Role missing on replica sets (RED-39002)

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

Private registries are not supported on OpenShift 3.11 (RED-38579)

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

Internal DNS and Kubernetes DNS may have conflicts (RED-37462)

DNS conflicts are possible between the cluster `mdns_server` and the K8s DNS. This only impacts DNS resolution from within cluster nodes for Kubernetes DNS names.

5.4.10 negatively impacts 5.4.6 (RED-37233)

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

Node CPU usage is reported instead of pod CPU usage (RED-36884)

In Kubernetes, the 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 (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 (i.e., "rec"). The workaround is to name the cluster "rec".

REC clusters fail to start on Kubernetes clusters with unsynchronized clocks (RED-47254)

When REC clusters are deployed on Kubernetes clusters with unsynchronized clocks, the REC cluster does not start correctly. The fix is to use NTP to synchronize the underlying K8s nodes.

Deleting an OpenShift project with an REC deployed may hang (RED-47192)

When 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 (RED-51921)

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

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

There is no workaround at this time

REC might report error states on initial startup (RED-61707)

There is no workaround at this time except to ignore the errors.

PVC size issues when using decimal value in spec (RED-62132)

The workaround for this issue is to make sure you use integer values for the PVC size.

Following old revision of quick start guide causes issues creating an REDB due to unrecognized memory field name

The workaround is to use the newer (current) revision of the quick start document available online.

Compatibility Notes

See [Supported Kubernetes distributions]() for the full list of supported distributions.

Now supported

This release adds support for the following:

* K8s 1.22 for GKE, AKS, and kOps
* OpenShift 4.9 (uses K8s 1.22)

Deprecated

* Rancher 2.5/K8s 1.17 support is deprecated

No longer supported

This release removes support for the following:

* Rancher 2.4 (previously deprecated)

kubectl patch crd redisenterpriseclusters.app.redislabs.com -p $'spec:\n preserveUnknownFields: false'


Redis Enterprise for Kubernetes Release Notes 6.2.8-15 (January 2022)

Summary: Maintenance release with bug fixes

Overview

The Redis Enterprise K8s 6.2.8-15 is a maintenance release for the [Redis Enterprise Software release 6.2.8]() and includes bug fixes.

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

Images

This release includes the following container images:

* **Redis Enterprise**: `redislabs/redis:6.2.8-64` or  `redislabs/redis:6.2.8-64.rhel7-openshift`
* **Operator**: `redislabs/operator:6.2.8-15`
* **Services Rigger**: `redislabs/k8s-controller:6.2.8-15` or `redislabs/services-manager:6.2.8-15` (on the Red Hat registry)

Fixed bugs

* Upgrading with the bundle using `kubectl apply -f` fails giving error (RED-69570):

    [code example]

* Removed unneeded certificates from the Redis Enterprise Software container (RED-69661, RED-60086)

Known limitations

Large clusters

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

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 will exceed 63 characters. The workaround is to limit cluster name to 20 characters or less.

Cluster CR (REC) errors are not reported after invalid updates (RED-25542)

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

An unreachable cluster has status running (RED-32805)

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

Readiness probe incorrect on failures (RED-39300)

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

Role missing on replica sets (RED-39002)

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

Private registries are not supported on OpenShift 3.11 (RED-38579)

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

Internal DNS and Kubernetes DNS may have conflicts (RED-37462)

DNS conflicts are possible between the cluster `mdns_server` and the K8s DNS. This only impacts DNS resolution from within cluster nodes for Kubernetes DNS names.

5.4.10 negatively impacts 5.4.6 (RED-37233)

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

Node CPU usage is reported instead of pod CPU usage (RED-36884)

In Kubernetes, the 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 (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 (i.e., "rec"). The workaround is to name the cluster "rec".

REC clusters fail to start on Kubernetes clusters with unsynchronized clocks (RED-47254)

When REC clusters are deployed on Kubernetes clusters with unsynchronized clocks, the REC cluster does not start correctly. The fix is to use NTP to synchronize the underlying K8s nodes.

Deleting an OpenShift project with an REC deployed may hang (RED-47192)

When 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 (RED-51921)

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

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

There is no workaround at this time

REC might report error states on initial startup (RED-61707)

There is no workaround at this time except to ignore the errors.

PVC size issues when using decimal value in spec (RED-62132)

The workaround for this issue is to make sure you use integer values for the PVC size.

Following old revision of quick start guide causes issues creating an REDB due to unrecognized memory field name

The workaround is to use the newer (current) revision of the quick start document available online.

Compatibility Notes

See [Supported Kubernetes distributions]() for the full list of supported distributions.

The CustomResourceDefinition "redisenterpriseclusters.app.redislabs.com" is invalid: spec.preserveUnknownFields: Invalid value: true: must be false in order to use defaults in the schema.


Redis Enterprise for Kubernetes Release Notes 6.2.8-2 (November 2021)

Summary: Support for RS 6.2.8, certificate management, and Redis upgrade policy.

Overview

The Redis Enterprise [K8s 6.2.8-2](https://github.com/RedisLabs/redis-enterprise-k8s-docs/releases/tag/v6.2.8-2) release provides support for the [Redis Enterprise Software release 6.2.8]() and includes several enhancements and bug fixes.

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

Images

This release includes the following container images:

* **Redis Enterprise**: `redislabs/redis:6.2.8-41` or  `redislabs/redis:6.2.8-41.rhel7-openshift`
* **Operator**: `redislabs/operator:6.2.8-2`
* **Services Rigger**: `redislabs/k8s-controller:6.2.8-2` or `redislabs/services-manager:6.2.8-2` (on the Red Hat registry)

New features

* Certificate management capabilities through the Redis Enterprise cluster API (RED-61176)

Feature improvements

* Support for managing database ports through the REDB API (RED-48286)
* Use explicit object instead of wildcard for roles (RED-38013)
* Advanced use case support for custom attributes for REC stateful set and rigger pods (RED-56502, RED-62550, RED-63426)
* Services rigger/K8s controller image changed to ubi-minimal lightweight base image (RED-61866)
* Support for the Redis upgrade policy setting through the REC API (RED-63000)

Fixed bugs

* Fixed issue of log rotation not working on OpenShift (RED-64726)

Known limitations

Large clusters

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

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 will exceed 63 characters. The workaround is to limit cluster name to 20 characters or less.

Cluster CR (REC) errors are not reported after invalid updates (RED-25542)

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

An unreachable cluster has status running (RED-32805)

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

Readiness probe incorrect on failures (RED-39300)

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

Role missing on replica sets (RED-39002)

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

Private registries are not supported on OpenShift 3.11 (RED-38579)

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

Internal DNS and Kubernetes DNS may have conflicts (RED-37462)

DNS conflicts are possible between the cluster `mdns_server` and the K8s DNS. This only impacts DNS resolution from within cluster nodes for Kubernetes DNS names.

5.4.10 negatively impacts 5.4.6 (RED-37233)

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

Node CPU usage is reported instead of pod CPU usage (RED-36884)

In Kubernetes, the 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 (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 (i.e., "rec"). The workaround is to name the cluster "rec".

REC clusters fail to start on Kubernetes clusters with unsynchronized clocks (RED-47254)

When REC clusters are deployed on Kubernetes clusters with unsynchronized clocks, the REC cluster does not start correctly. The fix is to use NTP to synchronize the underlying K8s nodes.

Deleting an OpenShift project with an REC deployed may hang (RED-47192)

When 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 (RED-51921)

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.

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

There is no workaround at this time

REC might report error states on initial startup (RED-61707)

There is no workaround at this time except to ignore the errors.

PVC size issues when using decimal value in spec (RED-62132)

The workaround for this issue is to make sure you use integer values for the PVC size.

Compatibility Notes

See [Supported Kubernetes distributions]() for the full list of supported distributions.

No longer supported

* kOps K8s versions 1.16 and 1.17 (previously deprecated) are no longer supported
* AKS K8s version 1.18 (previously deprecated) is no longer supported
* GKE K8s version 1.18 (previously deprecated) is no longer supported
* VMWare TKGI version 1.7 (K8s 1.16) (previously deprecated) is no longer supported
* VMWare TKGI version 1.8 (K8s 1.17) (previously deprecated) is no longer supported

Deprecation notice

* Rancher version 2.4 support is deprecated


Redis Enterprise for Kubernetes release notes 6.4.2-5 (April 2023)

Summary: The Redis Enterprise K8s 6.4.2-5 is a maintenance release for version 6.4.2-4.

Overview

This is a maintenance release of Redis Enterprise for Kubernetes 6.4.2-4 that adds supports for Redis Enterprise 6.4.2-61.

New images and fixes are listed below. Refer to [6.2.4-4 (March 2023)]() for compatibility notes and known limitations.

Images

* **Redis Enterprise**: `redislabs/redis:6.4.2-61`
* **Operator**: `redislabs/operator:6.4.2-5`
* **Services Rigger**: `redislabs/k8s-controller:6.4.2-5`

OpenShift images

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

OpenShift OLM bundles

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

Feature enhancements

* Upgraded to support Redis Enterprise 6.4.2-61

Bug fixes

* Fixed bug that can cause Redis cluster to become unresponsive during a Kubernetes upgrade on clusters with more than 9 REC nodes. (RED-93025)

Compatibility notes

See [Redis Enterprise for Kubernetes release notes 6.4.2-4 (March 2023)]().

Before upgrading

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

* **Supported upgrade paths**

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

* **ValidatingWebhookConfiguration**

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

Known limitations

Security

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


Redis Enterprise for Kubernetes release notes 6.4.2-6 (June 2023)

Overview

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

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

Images

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

OpenShift images

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

OpenShift OLM bundles

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

New features

* General availability of the Active-Active database controller for declarative configuration support

Feature improvements

* Active-Active controller improvements include adding support for the following:
  * Configuration via OLM
  * Certificates in `globalConfiguration`
  * Backups in `globalConfiguration`
  * Modules (preview)
  * Hashicorp Vault secrets
  * indication of sync failures to REAADB
* Added support for separate `podAnnotations` for Redis Enterprise pods to allow setting `appArmor` exceptions
* Timezone can be passed as environment variable into Redis Enterprise pods
* REDB namespaces can be labelled without the operator going into `CrashLoopBackoff`
* Added support for K8s 1.27
* Added support for K8s 1.25 for EKS
* Added support for K8s 1.26 for AKS and GKE
* Improved log collector execution log, filtering out empty files, capturing volume attachments, option to disable RS capture debug info package
* Added `extraEnvVars` field in REC to support environment variables for RS pods
* Changed RKE2 to the default for Rancher distributions

Fixed bugs

* REC in invalid state can't be deleted (RED-78124)
* OpenShift route not deleted after REC is deleted (RED-94121)
* REAADB secret status not being updated in source cluster (RED-96296)
* Invalid REAADB that is not rejected by admission might be deleted after apply (RED-96300)
* Operator logs an error about missing permissions to nodes on startup (RED-98227)
* Operator continues to update REC certificates in a loop (RED-98586)
* Log collector script may crash when trying to write multi-byte characters to file (RED-99869)
* Log collector fails to include RS debuginfo when old kubectl is used (RED-101170)
* REC creation fails due to required LDAP configuration in OLM form view (RED-100517)
* Upgrading to 6.4.2 (or 6.2.18) on OpenShift will fail if pod 0 is not the master node when upgrade starts (RED-102100)
* Upgrading from 6.2.8-15 (and below) to 6.2.12-1 (and above) may break the databases (RED-102241)

API changes

The following fields were changed in the [RedisEnterpriseCluster (REC) API]():
  * `containerTimezoneSpec.timezoneName` added to configure timezones on the Redis Enterprise pods
  * `hostAliases` added for adding an entry to the Redis Enterprise pods' `/etc/hosts`
  * `redisEnteprisePodAnnotations` added to specify annotations that should only be set on the Redis Enterprise pods
  * `ingressOrRouteSpec` enabled to use without alpha features enabled
  * `extraEnvVars` added for advanced users to add environment variables to the Redis Enterprise pods
  * `ServicesRiggerConfigurationSpec.podAnnotations` added to specify annotations that should only be set on the service rigger pods

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

Compatibility notes

Deprecated features

* Support for Gesher, the advanced admission control configuration, 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]().

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

\* Support added in this release

 Redis Enterprise for Kubernetes now uses RKE2 as the default for Rancher distributions.

Before upgrading

Be aware the following changes included in this release affect the upgrade process. Please read carefully before upgrading to 6.4.2-6.

* **ValidatingWebhookConfiguration**

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

* **OpenShift SCC**

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

Known limitations

New limitations

* **Admission controller may not alert when patching the REAADB with missing secret or RERC (RED-104463)** Remove the secret from the spec and create the missing secret, and then re-patch the REAADB again.

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

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

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

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

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

Existing limitations

* **RERC resources must have a unique name (`<rec-name>/<rec-namespace>`) (RED-96302)**

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

* **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 the [quick start]().

* **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 with unsynchronized clocks, the REC cluster does not start correctly. The fix is to use NTP to synchronize the underlying K8s nodes.

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

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

* **5.4.10 negatively impacts 5.4.6 (RED-37233)** Kubernetes-based 5.4.10 deployments seem to negatively impact existing 5.4.6 deployments that share a Kubernetes cluster.

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

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

Security

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


Redis Enterprise for Kubernetes release notes 6.4.2-8 (July 2023)

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

Overview

Redis Enterprise for Kubernetes version 6.4.2-8 is a maintenance release of version 6.2.4-6. It includes critical bug fixes and an updated Redis Enterprise image.

New in this release

Feature enhancements

* New Redis Enterprise software version 6.4.2-94 (RED-105738)

Bug fixes

* Fixed bad handling of certificate chains in the REC controller (RED-105578)

Upgrade considerations

Be aware the following changes included in this release affect the upgrade process. Please read carefully before upgrading to 6.4.2-8.

* **ValidatingWebhookConfiguration**

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

* **OpenShift SCC**

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

Compatibility

Deprecated features

Supported distributions

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

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

\* Support added in this release

 Redis Enterprise for Kubernetes now uses RKE2 as the default for Rancher distributions.

Images

* **Redis Enterprise**: `redislabs/redis:6.4.2-94`
* **Operator**: `redislabs/operator:6.4.2-8`
* **Services Rigger**: `redislabs/k8s-controller:6.4.2-8.`

#### OpenShift images

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

#### OLM bundle

* **Redis Enterprise operator bundle** : `v6.4.2-8`

Known limitations

* **Air-gapped environments using Gears will get stuck during cluster recovery(RED-112076)** This bug affects Redis Enterprise for Kubernetes versions older than 7.2.4-2.

Existing limitations

* **RERC resources must have a unique name (RED-96302)** The string "rec-name"/"rec-namespace" must be different from all other participating clusters in teh 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 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.

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

Security

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


Redis Enterprise for Kubernetes release notes 6.4.2-8 (Dec 2023)

Overview

This is a maintenance release of Redis Enterprise for Kubernetes version 6.4.2-8 and includes an updated Redis Enterprise image.

New in this release

Feature enhancements

* New Redis Enterprise software version 6.4.2-103

Upgrade considerations

Be aware the following changes included in this release affect the upgrade process. Please read carefully before upgrading to 6.4.2-8.

* **Upgrade path to versions 7.2.4-2 or later**

  Upgrading from this versions 7.2.4-2 or 7.2.4-7 is not possible using the OpenShift Operator Lifecycle Manager (OLM). OLM users will need to skip to version 7.2.4-10 to upgrade from this release version.

* **ValidatingWebhookConfiguration**

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

* **OpenShift SCC**

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

Compatibility

See [6.4.2-8 (July 2023) release notes]().

Images

* **Redis Enterprise**: `redislabs/redis:6.4.2-103`
* **Operator**: `redislabs/operator:6.4.2-8`
* **Services Rigger**: `redislabs/k8s-controller:6.4.2-8.`

#### OpenShift images

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

#### OLM bundle

* **Redis Enterprise operator bundle** : `v6.4.2-8.1`

Known limitations

Security

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


Redis Enterprise for Kubernetes release notes 6.4.2-8 (Oct 2024)

Summary: The Redis Enterprise K8s 6.4.2-8 release supports Redis Enterprise Software 6.4.2.

Overview

New in this release

Feature enhancements

* New Redis Enterprise software version 6.4.2-115

Upgrade considerations

Be aware the following changes included in this release affect the upgrade process. Please read carefully before upgrading to 6.4.2-8.

* **Upgrade path to versions 7.2.4-2 or later**

  Upgrading from this versions 7.2.4-2 or 7.2.4-7 is not possible using the OpenShift Operator Lifecycle Manager (OLM). OLM users will need to skip to version 7.2.4-10 to upgrade from this release version.

* **ValidatingWebhookConfiguration**

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

* **OpenShift SCC**

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

Compatibility

Images

* **Redis Enterprise**: `redislabs/redis:6.4.2-115`
* **Operator**: `redislabs/operator:6.4.2-8`
* **Services Rigger**: `redislabs/k8s-controller:6.4.2-8.`

#### OpenShift images

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

#### OLM bundle

* **Redis Enterprise operator bundle** : `v6.4.2-8.11`

The OLM version v6.4.2-8.11 replaces the earlier v6.4.2-8.10 release for the same Redis software version, providing only upgrade path fixes.

Known limitations