Redis Enterprise for Kubernetes release notes 6.4.2-8 (July 2023)
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
- New Redis Enterprise software version 6.4.2-94 (RED-105738)
- Fixed bad handling of certificate chains in the REC controller (RED-105578)
Be aware the following changes included in this release affect the upgrade process. Please read carefully before upgrading to 6.4.2-8.
This release uses a new
ValidatingWebhookConfigurationresource to replace the
redb-admissionwebhook 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.
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.
- Support for Gesher, the advanced admission control configuration, is deprecated.
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.
|VMware TKG 1.6||deprecated||deprecated|
|VMware TKGI version||1.13||1.14||1.15|
* Support added in this release
- Redis Enterprise:
- Services Rigger:
- Redis Enterprise:
redislabs/redis-enterprise:6.4.2-94.rhel7-openshiftif upgrading from RHEL 7)
- Services Rigger:
- Redis Enterprise operator bundle :
This release doesn’t introduce any new known limitations. See section below for existing known 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
shardCountwhich 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.
truecan cause unexpected bdb upgrades when
redisUpgradePolicyis 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 statuson node failure.
Internal DNS and Kubernetes DNS may have conflicts (RED-37462) DNS conflicts are possible between the cluster
mdns_serverand 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
runninginstead 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.