Releases: RedisLabs/redis-enterprise-k8s-docs
6.2.10-4
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-90orredislabs/redis:6.2.10-90.rhel7-openshift - Operator:
redislabs/operator:6.2.10-4 - Services Rigger:
redislabs/k8s-controller:6.2.10-4orredislabs/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 REC service is deprecated (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
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
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)
6.2.8-15
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-64orredislabs/redis:6.2.8-64.rhel7-openshift - Operator:
redislabs/operator:6.2.8-15 - Services Rigger:
redislabs/k8s-controller:6.2.8-15orredislabs/services-manager:6.2.8-15(on the Red Hat registry)
Fixed bugs
-
Upgrading with the bundle using
kubectl apply -ffails giving error (RED-69570):The CustomResourceDefinition "redisenterpriseclusters.app.redislabs.com" is invalid: spec.preserveUnknownFields: Invalid value: true: must be false in order to use defaults in the schema.
-
Removed unneeded certificates from the Redis Enterprise Software container (RED-69661, RED-60086)
Known limitations
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.
v6.2.8-11
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-53orredislabs/redis:6.2.8-53.rhel7-openshift - Operator:
redislabs/operator:6.2.8-11 - Services Rigger:
redislabs/k8s-controller:6.2.8-11orredislabs/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 Redis 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
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:
kubectl patch crd redisenterpriseclusters.app.redislabs.com -p $'spec:\n preserveUnknownFields: false'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)
v6.2.8-2
Overview
The Redis Enterprise K8s 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:
The following are the images and tags for this release:
| Component | k8s | Openshift |
|---|---|---|
| Redis Enterprise | redislabs/redis:6.2.8-41 |
redislabs/redis:6.2.8-41.rhel7-openshift |
| Operator | redislabs/operator:6.2.8-2 |
redislabs/operator:6.2.8-2 |
| Services Rigger | redislabs/k8s-controller:6.2.8-2 |
redislabs/services-manager:6.2.8-2 |
- RedHat certified images are available on Redhat Catalog
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
Hashicorp Vault integration - no support for Gesher (RED-55080)
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) is 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 a 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. Afterward, 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 not 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
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
Supported Distributions
Each release of the Redis Enterprise operator is thoroughly tested against a set of Kubernetes distributions. The table below lists the current release's support status for each distribution.
- "supported" indicates this distribution is supported for this release.
- "deprecated" indicates this distribution is supported for this release but will be dropped in a future release.
- "no longer supported" indicates support has been dropped for this distribution.
- Any distribution not listed below is not supported for production workloads.
| Distribution | Support Status |
|---|---|
| Openshift 3.11 (K8s 1.11) | deprecated |
| OpenShift 4.5 (K8s 1.18) | supported |
| OpenShift 4.6 (K8s 1.19) | supported |
| OpenShift 4.7 (K8s 1.20) | supported |
| OpenShift 4.8 (K8s 1.21) | supported |
| KOPS vanilla 1.18 | supported |
| KOPS vanilla 1.19 | supported |
| KOPS vanilla 1.20 | supported |
| KOPS vanilla 1.21 | supported |
| GKE 1.19 | supported |
| GKE 1.20 | supported |
| GKE 1.21 | supported |
| Rancher 2.4 (K8s 1.17) | deprecated |
| Rancher 2.4 (K8s 1.18) | deprecated |
| Rancher 2.5 (K8s 1.17) | supported |
| Rancher 2.5 (K8s 1.18) | supported |
| Rancher 2.5 (K8s 1.19) | supported |
| Rancher 2.5 (K8s 1.20) | supported |
| VMWare TKGI** 1.10 (K8s 1.19) | supported |
| AKS 1.19 | supported |
| AKS 1.21 | supported |
| EKS 1.18 | supported |
| EKS 1.21 | supported |
* No longer supported by the vendor
** Tanzu Kubernetes Grid Integrated Edition
v6.2.4-1
Overview
The Redis Enterprise K8s 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:
The following are the images and tags for this release:
| Component | k8s | Openshift |
|---|---|---|
| Redis Enterprise | redislabs/redis:6.2.4-55 |
redislabs/redis:6.2.4-55.rhel7-openshift |
| Operator | redislabs/operator:6.2.4-1 |
redislabs/operator:6.2.4-1 |
| Services Rigger | redislabs/k8s-controller:6.2.4-1 |
redislabs/k8s-controller:6.2.4-1 |
- RedHat certified images are available on Redhat Catalog
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 Redis Enterprise pods not recovering from container fails (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
Hashicorp Vault integration - no support for Gesher (RED-55080)
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) is 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 a 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. Afterward, 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 not 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]({{<relref "/platforms/kubernetes/reference/supported_k8s_distributions.md">}}) 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 TKGIE 1.7 (K8s 1.16), VMWare TKGIE 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.
Supported Distributions
Each release of the Redis Enterprise operator is thoroughly tested against a set of Kubernetes distributions. The table below lists the current release's support status for each distribution.
- "supported" indicates this distribution is supported for this release.
- "deprecated" indicates this distribution is supported for this release, but will be dropped in a future release.
- "no longer supported" indicates support has been dropped for this distribution.
- Any distribution not listed below is not supported for production workloads.
| Distribution | Support Status |
|---|---|
| Openshift 3.11 (K8s 1.11) | deprecated |
| OpenShift 4.6 (K8s 1.19) | supported |
| OpenShift 4.7 (K8s 1.20) | supported |
| OpenShift 4.8 (K8s 1.21) | supported |
| KOPS vanilla 1.16 | deprecated |
| KOPS vanilla 1.17 | deprecated |
| KOPS vanilla 1.18 | supported |
| KOPS vanilla 1.19 | supported |
| KOPS vanilla 1.20 | supported |
| KOPS vanilla 1.21 | supported |
| GKE 1.18 | supported |
| GKE 1.19 | supported |
| GKE 1.20 | supported |
| GKE 1.21 | supported |
| Rancher 2.4 (K8s 1.17) | supported |
| Rancher 2.4 (K8s 1.18) | supported |
| Rancher 2.5 (K8s 1.17) | supported |
| Rancher 2.5 (K8s 1.18) | supported |
| Rancher 2.5 (K8s 1.19) | supported |
| Rancher 2.5 (K8s 1.20) | supported |
| VMWare TKGIE* 1.7 (K8s 1.16) | deprecated |
| VMWare TKGIE* 1.8 (K8s 1.17) | deprecated |
| VMWare TKGIE** 1.10 (K8s 1.19) | supported |
| AKS 1.18 | supported |
| AKS 1.19 | supported |
| AKS 1.20 | supported |
| EKS 1.18 | supported |
| EKS 1.19 | supported |
| EKS 1.20 | supported |
| EKS 1.21 | supported |
* No longer supported by VMware
** Tanzu Kubernetes Grid Integrated Edition
v6.0.20-12
Overview
The Redis Enterprise K8s 6.0.20-12 release is a major release on top of 6.0.20-4 providing support for the Redis Enterprise Software release 6.0.20-97 and includes several enhancements and bug fixes.
This release of the operator provides:
- New features
- Various bug fixes
Images
This release includes the following container images:
- Redis Enterprise: redislabs/redis:6.0.20-97 or redislabs/redis:6.0.20-97.rhel7-openshift
- Operator and Bootstrapper: redislabs/operator:6.0.20-12
- Services Rigger: redislabs/k8s-controller:6.0.20-12 or redislabs/services-manager:6.0.20-12 (on the Red Hat registry)
New features
- EKS support
- Feature parity for Openshift OLM; added support for:
- REDB
- admission
- Hashicorp Vault integration
- Hashicorp Vault integration is now GA
- Moved Operator environment variables to configmap
Important fixes
- Admission controller deployment combined with operator deployment to simplify deployment (RED-52701)
- Additional verbosity in the
kubectl get redbcommand output (RED-55042) - Support for Redis Enterprise license storage within secrets; Vault and K8s secrets (RED-55587)
- Support for manual procedure to replace the REC credentials (RED-56529, RED-56530)
- Fixed cluster recovery issue - recovery process was not starting (RED-55500)
- When a pod status is CrashLoopBackOff and we run the cluster recovery, the process will not complete (RED-33713)
- Master pod is not always labeled in Rancher (fixed in 6.0.8 but was not documented) (RED-42896)
Known limitations
Hashicorp Vault integration - no support for Gesher (RED-55080)
There is no workaround at this time
Nodes down indefinitely after the redis-enterprise-node container of a REC pod is restarted (53042)
In some cases where the Redis Enterprise Cluster container in the Redis Enterprise Cluster(REC) pod is restarted, the REC node remains down. Workaround: restart the pod, while ensuring the majority of REC nodes are available.
CrashLoopBackOff causes cluster recovery to be incomplete (RED33713)
When a pod's status is CrashLoopBackOff and we run the cluster recovery, the process will not complete. The workaround is to delete the crashing pods manually. The recovery process will then continue.
Long cluster names cause routes to be rejected (RED25871)
A cluster name longer than 20 characters will result in a rejected route configuration because the host part of the domain name will exceed 63 characters. The workaround is to limit cluster name to 20 characters or fewer.
Cluster CR (REC) errors are not reported after invalid updates (RED25542)
A cluster CR specification error is not reported if two or more invalid CR resources are updated in sequence.
An unreachable cluster has status running (RED32805)
When a cluster is in an unreachable state, the state is still running instead of being reported as an error.
Readiness probe incorrect on failures (RED39300)
STS Readiness probe does not mark a node as "not ready" when running rladmin status on the node fails.
Role missing on replica sets (RED39002)
The redis-enterprise-operator role is missing permission on replica sets.
Private registries are not supported on OpenShift 3.11 (RED38579)
Openshift 3.11 does not support DockerHub private registries. This is a known OpenShift issue.
Internal DNS and Kubernetes DNS may have conflicts (RED37462)
DNS conflicts are possible between the cluster mdns_server and the K8s DNS. This only impacts DNS resolution from within cluster nodes for Kubernetes DNS names.
5.4.10 negatively impacts 5.4.6 (RED37233)
Kubernetes-based 5.4.10 deployments seem to negatively impact existing 5.4.6 deployments that share a Kubernetes cluster.
Node CPU usage is reported instead of pod CPU usage (RED36884)
In Kubernetes, the node CPU usage we report on is the usage of the Kubernetes worker node hosting the REC pod.
Clusters must be named "rec" in OLM-based deployments (RED39825)
In OLM-deployed operators, the deployment of the cluster will fail if the name is not "rec". When the operator is deployed via the OLM, the security context constraints (scc) is bound to a specific service account name (i.e., "rec"). The workaround is to name the cluster "rec".
Master pod label in Rancher (RED42896)
The master pod is not always labeled in Rancher.
REC clusters fail to start on Kubernetes clusters with unsynchronized clocks (RED47254)
When REC clusters are deployed on Kubernetes clusters with unsynchronized clocks, the REC cluster does not start correctly. The fix is to use NTP to synchronize the underlying K8s nodes.
Deleting an OpenShift project with an REC deployed may hang (RED47192)
When a REC cluster is deployed in a project (namespace) and has REDB resources, the
REDB resources must be deleted first before the REC can be deleted. As such, until the
REDB resources are deleted, the project deletion will hang. The fix is to delete the
REDB resources first and the REC second. Afterwards, you may delete the project.
REC extraLabels are not applied to PVCs on K8s versions 1.15 or older (RED51921)
In K8s 1.15 or older, the PVC labels come from the match selectors and not the
PVC templates. As such, these versions can not support PVC labels. If this feature
is required, the only fix is to upgrade the K8s cluster to a newer version.
Compatibility Notes
- EKS is now supported (K8s 1.18)
- OpenShift 4.4 (previously deprecated) is no longer supported
- GKE K8s versions 1.15, 1.16 (previously deprecated) is no longer supported
- VMWare TKGIE 1.10 (K8s 1.19) is now supported
Deprecation notice
- GKE K8s version 1.17 (no longer supported by Google) is deprecated
- kOps 1.15 is deprecated
- VMWare TKGIE 1.7 (K8s 1.16), VMWare TKGIE 1.8 (K8s 1.17) are deprecated (no longer supported by VMWare)
v6.0.20-4
Overview
The Redis Enterprise K8s 6.0.20-4 release is a major release on top of 6.0.8-20 providing support for the Redis Enterprise Software release 6.0.20-69 and includes several enhancements and bug fixes.
This release of the operator provides:
- New features
- Various bug fixes
Images
This release includes the following container images:
- Redis Enterprise: redislabs/redis:6.0.20-69 or redislabs/redis:6.0.20-69.rhel7-openshift
- Operator and Bootstrapper: redislabs/operator:6.0.20-4
- Services Rigger: redislabs/k8s-controller:6.0.20-4 or redislabs/services-manager:6.0.20-4 (on the Red Hat registry)
New features
- Support for Openshift 4.7
- Support for Kubernetes 1.20
New preview features
- Hashicorp Vault integration - REC secret
- Hashicorp Vault integration - REDB secrets
Important fixes
- Fixed upgrade issue with custom container repositories specifying port numbers (RED-53192)
- REDB controller no longer performs reconciliation until Redis Enterprise software version complies with operator (RED-53194)
- Removed unused node.js package from Services Rigger image (RED-53536)
- Fixed operator crash on change of uiServiceType (RED-54621)
- Avoid excessive logging within RS pod (envoy_access.log) (RED-55525)
Known limitations
OpenShift 4.7 - v6.0.20-4 cannot be deployed by OLM
6.0.20-4 does not appear in OLM. Workaround - deploy manually. A future maintenance release will address this.
Hashicorp Vault integration - no support for Gesher (RED-55080)
There is no workaround at this time
Nodes down indefinitely after the redis-enterprise-node container of a REC pod is restarted (53042)
In some cases where the Redis Enterprise Cluster container in the Redis Enterprise Cluster(REC) pod is restarted, the REC node remains down. Workaround: restart the pod, while ensuring the majority of REC nodes are available.
CrashLoopBackOff causes cluster recovery to be incomplete (RED33713)
When a pod's status is CrashLoopBackOff and we run the cluster recovery, the process will not complete. The workaround is to delete the crashing pods manually. The recovery process will then continue.
Long cluster names cause routes to be rejected (RED25871)
A cluster name longer than 20 characters will result in a rejected route configuration because the host part of the domain name will exceed 63 characters. The workaround is to limit cluster name to 20 characters or fewer.
Cluster CR (REC) errors are not reported after invalid updates (RED25542)
A cluster CR specification error is not reported if two or more invalid CR resources are updated in sequence.
An unreachable cluster has status running (RED32805)
When a cluster is in an unreachable state, the state is still running instead of being reported as an error.
Readiness probe incorrect on failures (RED39300)
STS Readiness probe does not mark a node as "not ready" when running rladmin status on the node fails.
Role missing on replica sets (RED39002)
The redis-enterprise-operator role is missing permission on replica sets.
Private registries are not supported on OpenShift 3.11 (RED38579)
Openshift 3.11 does not support DockerHub private registries. This is a known OpenShift issue.
Internal DNS and Kubernetes DNS may have conflicts (RED37462)
DNS conflicts are possible between the cluster mdns_server and the K8s DNS. This only impacts DNS resolution from within cluster nodes for Kubernetes DNS names.
5.4.10 negatively impacts 5.4.6 (RED37233)
Kubernetes-based 5.4.10 deployments seem to negatively impact existing 5.4.6 deployments that share a Kubernetes cluster.
Node CPU usage is reported instead of pod CPU usage (RED36884)
In Kubernetes, the node CPU usage we report on is the usage of the Kubernetes worker node hosting the REC pod.
Clusters must be named "rec" in OLM-based deployments (RED39825)
In OLM-deployed operators, the deployment of the cluster will fail if the name is not "rec". When the operator is deployed via the OLM, the security context constraints (scc) is bound to a specific service account name (i.e., "rec"). The workaround is to name the cluster "rec".
Master pod label in Rancher (RED42896)
The master pod is not always labeled in Rancher.
REC clusters fail to start on Kubernetes clusters with unsynchronized clocks (RED47254)
When REC clusters are deployed on Kubernetes clusters with unsynchronized clocks, the REC cluster does not start correctly. The fix is to use NTP to synchronize the underlying K8s nodes.
Deleting an OpenShift project with an REC deployed may hang (RED47192)
When a REC cluster is deployed in a project (namespace) and has REDB resources, the
REDB resources must be deleted first before the REC can be deleted. As such, until the
REDB resources are deleted, the project deletion will hang. The fix is to delete the
REDB resources first and the REC second. Afterwards, you may delete the project.
REC extraLabels are not applied to PVCs on K8s versions 1.15 or older (RED51921)
In K8s 1.15 or older, the PVC labels come from the match selectors and not the
PVC templates. As such, these versions can not support PVC labels. If this feature
is required, the only fix is to upgrade the K8s cluster to a newer version.
Compatibility Notes
- OpenShift 4.7 and Rancher/kOps 1.20 are now supported
- OpenShift 4.1, 4.2, 4.3 (previously deprecated) are no longer supported
- GKE K8s version 1.14 (previously deprecated) is no longer supported
- kOps (upstream K8s) 1.13, 1.14 (previously deprecated) are no longer supported
Deprecation notice
- OpenShift 4.4 (no longer supported by Red Hat) is deprecated
- GKE K8s versions 1.15, 1.16 (no longer supported by Google) are deprecated
- kOps (upstream K8s) 1.15 is deprecated
v6.0.12-5
Overview
The Redis Enterprise K8s 6.0.12-5 release is a major release on top of 6.0.8-20 providing support for the Redis Enterprise Software release 6.0.12-57 and includes several enhancements and bug fixes.
This release of the operator provides:
- New features
- Various bug fixes
Images
This release includes the following container images:
- Redis Enterprise: redislabs/redis:6.0.12-57 or redislabs/redis:6.0.12-57.rhel7-openshift
- Operator and Bootstrapper: redislabs/operator:6.0.12-5
- Services Rigger: redislabs/k8s-controller:6.0.12-5 or redislabs/services-manager:6.0.12-5 (Red Hat registry)
New features
- Azure Kubernetes Service (AKS) is now supported. (RED40323)
- Database custom resources now support roles permissions (role to Redis ACL bindings). (RED49780)
Feature Improvements
- The license information has been added to the REC status. (RED43078)
kubectl get recnow displays more information (i.e., added "NODES", "VERSION", "STATE", "SPEC STATUS"). (RED46428)- The
extraLabelsin the cluster spec now applies to the PV and PVC at creation. (RED48694) - Added Rancher 2.5 support. (RED50211)
- Added K8s (Kops) 1.19 support. (RED50211)
- Added OpenShift 4.6 support. (RED50495)
- Database resources can now disable the default database user. (RED50215)
- REC credentials no longer use environment variables in pods. (RED47969)
Important fixes
- Fixed an issue where pods are stuck terminating during teardown. (RED44726)
- Fixed an issue where pods are stuck terminating during cluster recovery. (RED43846)
- Changed the operator logs to use human-readable dates and times. (RED39026)
- Fixed the display of resources in the OLM (OpenShift). (RED48116)
- Fixed backup configuration issue for GCS without a subdir. (RED49299)
Known limitations
CrashLoopBackOff causes cluster recovery to be incomplete (RED33713)
When a pod's status is CrashLoopBackOff and we run the cluster recovery, the process will not complete. The workaround is to delete the crashing pods manually. The recovery process will then continue.
Long cluster names cause routes to be rejected (RED25871)
A cluster name longer than 20 characters will result in a rejected route configuration because the host part of the domain name will exceed 63 characters. The workaround is to limit cluster name to 20 characters or fewer.
Cluster CR (REC) errors are not reported after invalid updates (RED25542)
A cluster CR specification error is not reported if two or more invalid CR resources are updated in sequence.
An unreachable cluster has status running (RED32805)
When a cluster is in an unreachable state, the state is still running instead of being reported as an error.
Readiness probe incorrect on failures (RED39300)
STS Readiness probe does not mark a node as "not ready" when running rladmin status on the node fails.
Role missing on replica sets (RED39002)
The redis-enterprise-operator role is missing permission on replica sets.
Private registries are not supported on OpenShift 3.11 (RED38579)
Openshift 3.11 does not support DockerHub private registries. This is a known OpenShift issue.
Internal DNS and Kubernetes DNS may have conflicts (RED37462)
DNS conflicts are possible between the cluster mdns_server and the K8s DNS. This only impacts DNS resolution from within cluster nodes for Kubernetes DNS names.
5.4.10 negatively impacts 5.4.6 (RED37233)
Kubernetes-based 5.4.10 deployments seem to negatively impact existing 5.4.6 deployments that share a Kubernetes cluster.
Node CPU usage is reported instead of pod CPU usage (RED36884)
In Kubernetes, the node CPU usage we report on is the usage of the Kubernetes worker node hosting the REC pod.
Clusters must be named "rec" in OLM-based deployments (RED39825)
In OLM-deployed operators, the deployment of the cluster will fail if the name is not "rec". When the operator is deployed via the OLM, the security context constraints (scc) is bound to a specific service account name (i.e., "rec"). The workaround is to name the cluster "rec".
Master pod label in Rancher (RED42896)
The master pod is not always labeled in Rancher.
REC clusters fail to start on Kubernetes clusters with unsynchronized clocks (RED47254)
When REC clusters are deployed on Kubernetes clusters with unsynchronized clocks, the REC cluster does not start correctly. The fix is to use NTP to synchronize the underlying K8s nodes.
Deleting an OpenShift project with an REC deployed may hang (RED47192)
When a REC cluster is deployed in a project (namespace) and has REDB resources, the
REDB resources must be deleted first before the REC can be deleted. As such, until the
REDB resources are deleted, the project deletion will hang. The fix is to delete the
REDB resources first and the REC second. Afterwards, you may delete the project.
REC extraLabels are not applied to PVCs on K8s versions 1.15 or older (RED51921)
In K8s 1.15 or older, the PVC labels come from the match selectors and not the
PVC templates. As such, these versions can not support PVC labels. If this feature
is required, the only fix is to upgrade the K8s cluster to a newer version.
Compatibility Notes
- OpenShift 4.6 and Rancher/kOps 1.19 are now supported.
- Rancher 2.5 is now supported.
- AKS (K8s 1.18) is now supported.
Deprecation notice
- OpenShift 4.1, 4.2, and 4.3 are now deprecated.
- GKE K8s version 1.14 is deprecated.
- kOps 1.13 and 1.14 are deprecated.
v6.0.8-20
Overview
The Redis Enterprise K8s 6.0.8-20 release is a major release on top of 6.0.8-1 providing support for the latest Redis Enterprise Software release 6.0.8-30 and includes several enhancements and bug fixes.
This release of the operator provides:
- The latest release version of the operator
- New features
- Various bug fixes
Images
- Redis Enterprise - redislabs/redis:6.0.8-30 or redislabs/redis:6.0.8-30.rhel7-openshift
- Operator - redislabs/operator:6.0.8-20
- Services Rigger - redislabs/k8s-controller:6.0.8-20 or redislabs/services-manager:6.0.8-20 (Red Hat registry)
New features
- Databases custom resources (REDB) can be created in separate consumer namespaces from the operator and cluster namespace. The operator deployment is configured to watch specific namespaces for these database REDB CR’s.
- The Gesher admission control proxy is now certified by Red Hat.
- REDB CR’s no longer require a Redis Enterprise cluster name. The name will default to the cluster in the context of the operator.
- REC and REDB CR’s are now validated via a schema.
Important fixes
- Using database controller (REDB) no longer generates errors: “failed to update database status" (RED44919)
- Issues with configuring replica-of through the database controller (REDB) and TLS have been fixed. (RED48285)
- A time out issue with “rlutil upgrade” was fixed. (RED48700)
Known limitations
CrashLoopBackOff causes cluster recovery to be incomplete (RED33713)
When a pod status is CrashLoopBackOff and we run the cluster recovery, the process will not complete. The workaround is to delete the crashing pods manually and recovery process will continue.
Long cluster names cause routes to be rejected (RED25871)
A cluster name longer than 20 characters will result in a rejected route configuration as the host part of the domain name exceeds 63 characters. The workaround is to limit cluster name to 20 characters or less.
Cluster CR (REC) errors are not reported after invalid updates (RED25542)
A cluster CR specification error is not reported if two or more invalid CR resources are updated in sequence.
An unreachable cluster has status running (RED32805)
When a cluster is in an unreachable state the state is still running instead of being reported as an error.
Readiness probe incorrect on failures (RED39300)
STS Readiness probe doesn't mark a node as not ready when rladmin status on the node fails.
Role missing on replica sets (RED39002)
The redis-enterprise-operator role is missing permission on replica sets.
Private registries are not supported on OpenShift 3.11 (RED38579)
Openshift 3.11 doesn't support dockerhub private registry. This is a known OpenShift issue.
Internal DNS and Kubernetes DNS may have conflicts (RED37462)
DNS conflicts are possible between the cluster mdns_server and the K8s DNS. This only impacts DNS resolution from within cluster nodes for Kubernetes DNS names.
5.4.10 negatively impacts 5.4.6 (RED37233)
Kubernetes-based 5.4.10 deployments seem to negatively impact existing 5.4.6 deployments that share a Kubernetes cluster.
Node CPU usage is reported instead of pod CPU usage (RED36884)
In Kubernetes, the node CPU usage we report on is the usage of the Kubernetes worker node hosting the REC pod.
Clusters must be named "rec" in OLM-based deployments (RED39825)
In OLM-deployed operators, the deployment of the cluster will fail if the name is not "rec". When the operator is deployed via the OLM, the security context constraints (scc) is bound to a specific service account name (i.e., "rec"). The workaround is to name the cluster "rec".
Master pod label in Rancher (RED42896)
Master pod is not always labeled in Rancher.
Cluster fail to start for clusters with unsynchronized clocks (RED47254)
When REC clusters are deployed on clusters with unsynchronized clocks, the cluster does not start correctly. The fix is to use NTP to synchronize the underlying K8s nodes.
Compatibility Notes
N/A
v6.0.8-1
Overview
The Redis Enterprise K8s 6.0.8-1 release is a major release on top of 6.0.6-24 providing support for the latest Redis Enterprise Software release 6.0.8-28 and includes several enhancements (including OpenShift 4.5 and Kubernetes 1.18 support) and bug fixes.
This release of the operator provides:
- The latest release version of the operator
- New features
- New support K8s distributions and platforms
- Various bug fixes
Images
- Redis Enterprise - redislabs/redis:6.0.8-28 or redislabs/redis:6.0.8-28.rhel7-openshift
- Operator - redislabs/operator:6.0.8-1
- Services Rigger - redislabs/k8s-controller:6.0.8-1 or redislabs/services-manager:6.0.8-1 (Red Hat registry)
New features
- Redis Modules can now be configured in the database custom resource.
- Support was added for OpenShift 4.5
- Support was added for Kubernetes 1.18
- Added support for the Gesher admission control proxy to provide an administrator the ability to setup delegation to avoid the need for administrator intervention on every namespaced deployed operator.
Important fixes
- Added the missing Services Rigger health check (RED47062)
- Fixed failures when updating the ui service type (RED45771)
Known limitations
CrashLoopBackOff causes cluster recovery to be incomplete (RED33713)
When a pod status is CrashLoopBackOff and we run the cluster recovery, the process will not complete. The workaround is to delete the crashing pods manually and recovery process will continue.
Long cluster names cause routes to be rejected (RED25871)
A cluster name longer than 20 characters will result in a rejected route configuration as the host part of the domain name exceeds 63 characters. The workaround is to limit cluster name to 20 characters or less.
Cluster CR (REC) errors are not reported after invalid updates (RED25542)
A cluster CR specification error is not reported if two or more invalid CR resources are updated in sequence.
An unreachable cluster has status running (RED32805)
When a cluster is in an unreachable state the state is still running instead of being reported as an error.
Readiness probe incorrect on failures (RED39300)
STS Readiness probe doesn't mark a node as not ready when rladmin status on the node fails.
Role missing on replica sets (RED39002)
The redis-enterprise-operator role is missing permission on replica sets.
Private registries are not supported on OpenShift 3.11 (RED38579)
Openshift 3.11 doesn't support dockerhub private registry. This is a known OpenShift issue.
Internal DNS and Kubernetes DNS may have conflicts (RED37462)
DNS conflicts are possible between the cluster mdns_server and the K8s DNS. This only impacts DNS resolution from within cluster nodes for Kubernetes DNS names.
5.4.10 negatively impacts 5.4.6 (RED37233)
Kubernetes-based 5.4.10 deployments seem to negatively impact existing 5.4.6 deployments that share a Kubernetes cluster.
Node CPU usage is reported instead of pod CPU usage (RED36884)
In Kubernetes, the node CPU usage we report on is the usage of the Kubernetes worker node hosting the REC pod.
Master pod label in Rancher (RED42896)
Master pod is not always labeled in Rancher.
Cluster fail to start for clusters with unsynchronized clocks (RED47254)
When REC clusters are deployed on clusters with unsynchronized clocks, the cluster does not start correctly. The fix is to use NTP to synchronize the underlying K8s nodes.
Errors in operator log for REDB status (RED44919)
Benign errors are reported in the operator log when using database controller (REDB) (e.g., “failed to update database status". These errors can be ignored.
Compatibility Notes
- Support for OpenShift 4.5 was added,
- Support for Kubernetes 1.18 was added,
- Support for the previous deprecated Kubernetes 1.11 and 1.12 has been removed.