Redis Enterprise for Kubernetes 8.0.18 release notes

Releases with support for Redis Enterprise Software 8.0.18

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

Detailed release notes

Supported distributions

Redis Enterprise for Kubernetes is compatible with CNCF-conformant Kubernetes platforms. The operator follows standard Kubernetes APIs and practices and is designed to run consistently across certified Kubernetes environments.

The following table shows supported Kubernetes versions at the time of this release. For a list of platforms tested with this release, see Supported Kubernetes distributions.

Known limitations

• SSO configuration does not work with IPv6 or dual-stack (IPv4/IPv6) clusters.

• Upgrades from versions earlier than 7.4.2-2 are not supported. If you use an earlier version, upgrade to 7.4.2-2 before upgrading to this version.

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

• The REDB redisVersion field cannot be used for memcached databases.

• Modifying the database suffix for an Active-Active database while the services rigger is terminating causes a loop. The services rigger deletes and recreates ingress or route resources repeatedly. Wait for the services rigger pod to finish terminating before modifying the suffix.

• REAADB changes might fail with "gateway timeout" errors, especially on OpenShift. Retry the operation.

• Creating two databases with the same name in the Redis Enterprise Cluster Manager UI deletes the service and makes the database unavailable. Avoid duplicate database names. The admission controller prevents duplicate names when you create databases through the Kubernetes operator.

• Installing the operator bundle produces the warning Warning: would violate PodSecurity "restricted: v1.24". Ignore this warning. Red Hat documentation identifies this issue as benign.

• RERC resources must have a unique name. The rec-name/rec-namespace string must differ from all other participating clusters in the Active-Active database.

• Admission does not block REAADB resources with a shardCount that exceeds the license quota. Correct the REAADB configuration and reapply.

• The Active-Active controller supports only global database options. Location-specific configuration is not supported.

• Removing an Active-Active setup might leave services or routes undeleted. Delete the services or routes manually.

• Setting autoUpgrade to true can cause unexpected database upgrades when redisUpgradePolicy is also true. Contact support if your deployment is affected.

• Using the previous quick start guide causes REDB creation issues due to an unrecognized memory field name. Use the current version of the Deploy Redis Enterprise Software for Kubernetes guide.

• PVC size does not work with decimal values. Use integer values for the PVC size.

• REC might report error states on initial startup. No workaround exists. Ignore the errors.

• HashiCorp Vault integration does not support Gesher. No workaround exists. Gesher support is deprecated.

• REC clusters fail to start on Kubernetes clusters with unsynchronized clocks. Use NTP to synchronize the underlying Kubernetes nodes.

• Deleting an OpenShift project with a deployed REC might hang. When an REC cluster is deployed in a project (namespace) with REDB resources, you must delete the REDB resources before deleting the REC. The project deletion hangs until you delete the REDB resources. Delete the REDB resources first, then delete the REC, and then delete the project.

• Clusters must be named "rec" in OLM-based deployments. When you deploy the operator through OLM, the security context constraints (SCC) are bound to a specific service account name ("rec"). The deployment fails if the cluster has a different name.

• Readiness probe does not correctly report failures. The StatefulSet readiness probe does not mark a node as "not ready" when running rladmin status on node failure.

• Internal DNS and Kubernetes DNS might conflict. DNS conflicts can occur between the cluster mdns_server and Kubernetes DNS. This affects only DNS resolution from within cluster nodes for Kubernetes DNS names.

• Kubernetes-based 5.4.10 clusters might negatively affect existing 5.4.6 clusters. Upgrade your clusters to the latest version.

• Node CPU usage is reported instead of pod CPU usage. The reported CPU usage is for the Kubernetes worker node hosting the REC pod, not the pod itself.

• An unreachable cluster shows status as running. When a cluster is unreachable, the status remains running instead of showing an error.

• Long cluster names cause routes to be rejected. A cluster name longer than 20 characters causes route rejection because the host part of the domain name exceeds 63 characters. Limit the cluster name to 20 characters or fewer.

• Cluster CR (REC) errors are not reported after invalid updates. A cluster CR specification error is not reported if you update two or more invalid CR resources in sequence.