Skip to content

v6.0.8-20
Compare
Choose a tag to compare
@alexmilowski alexmilowski released this 11 Dec 02:21
· 186 commits to master since this release
v6.0.8-20
0c5c1c1
This commit was created on GitHub.com and signed with GitHub’s verified signature. The key has expired.
GPG key ID: 4AEE18F83AFDEB23
Expired
Verified
Learn about vigilant mode.

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

Assets 2
Loading