Skip to content

Releases: RedisLabs/redis-enterprise-k8s-docs

7.4.2-12

02 May 17:16
@bascar bascar
v7.4.2-12
aadec5e
This commit was created on GitHub.com and signed with GitHub’s verified signature.
GPG key ID: B5690EEEBB952194
Learn about vigilant mode.
Compare
Choose a tag to compare
7.4.2-12 Latest
Latest

Highlights

This release 7.4.2-12 has many enhancements, most notably support for persistent volume expansion in the REC. Also, some essential changes in module handling support newer capabilities prompted by changes in the underlying Redis Enterprise around versioning.

New in this release

Enhancements

  • Support for persistent volume expansion in the REC (RED-84018)
  • Ability to specify Redis version in REDB spec (RED-103945)
  • Updated supported distributions (RED-119711)
  • Ability to enable modules via REDB without specifying a module version (RED-116082)
  • Dual Stack configuration support (RED-121897)

Resolved issues

  • Fixed case of client certificates being updated in a loop (RED-121633)
  • Fixed issues disabling replication on REDB (RED-122721)

API changes

CRD Field Change Description
REC spec.persistentSpec.enablePersistentVolumeResize ADD Set to "true" to allow changes in volumeSize after REC creation (for sizing up only)
REC status.persistenceStatus ADD Indicates the status of persistent volume expansion
REC spec.redisEnterpriseIPFamily ADD Configure which IP family to use when Kubernetes cluster has Dual Stack networking enabled
REDB spec.moduleList[x].version CHANGE Field is no longer mandatory
REDB spec.upgradeSpec ADD New field allows configuration of module upgrade settings
REDB spec.redisVersion CHANGE Now allows setting version numbers (Major.Minor)

Version changes

Breaking changes

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

ValidatingWebhookConfiguration

Versions 6.4.2-4 and later include 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

Versions 6.4.2-6 and later include 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 instructions.

Deprecations

  • Redis Enterprise no longer supports Ubuntu-based images.

Upcoming Changes

  • Future Redis Enterprise images will be UBI9-based only, without support for Ubuntu-based images.

Supported distributions

The following table shows supported distributions at the time of this release. You can also find this list in Supported Kubernetes distributions.

✅ Supported – This distribution is supported for this version of Redis Enterprise Software for Kubernetes.

⚠️ Deprecated – This distribution is still supported for this version of Redis Enterprise Software for Kubernetes, but support will be removed in a future release.

❌ End of life – Support for this distribution ended.

Any distribution not listed below is not supported for production workloads.

Kubernetes version 1.24 1.25 1.26 1.27 1.28 1.29
Community Kubernetes ⚠️ ✅ ✅ ✅
Amazon EKS ⚠️ ✅ ✅ ✅
Azure AKS ⚠️ ✅ ✅ ✅
Google GKE ⚠️ ✅ ✅ ✅ ✅
Rancher RKE2 ❌ ✅ ✅ ✅
VMware TKG 2.2 ⚠️ ⚠️
VMware TKG 2.3 ✅ ✅ ✅
VMware TKG 2.4 ✅ ✅ ✅
OpenShift version 4.11 4.12 4.13 4.14 4.15
⚠️ ✅ ✅ ✅ ✅
VMware TKGI version 1.15 1.16 1.17 1.18
❌ ✅ ✅ ✅

Downloads

  • Redis Enterprise: redislabs/redis:7.4.2-129
  • Operator: redislabs/operator:7.4.2-12
  • Services Rigger: redislabs/k8s-controller:7.4.2-12

OpenShift images

  • Redis Enterprise: registry.connect.redhat.com/redislabs/redis-enterprise:7.4.2-129.rhel8-openshift
  • Operator: registry.connect.redhat.com/redislabs/redis-enterprise-operator:7.4.2-12
  • Services Rigger: registry.connect.redhat.com/redislabs/services-manager:7.4.2-12

OLM bundle

Redis Enterprise operator bundle : v7.4.2-12.0

Known limitations

New limitations

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

Existing limitations

  • The REDB “redisVersion” field can’t be used for memcached databases(RED-119152)

  • When modifying the database suffix for an Active-Active database, while the service-rigger is in a terminating state, the services-rigger will delete and create the ingress or route resources in a loop (RED-107687) Wait until the services rigger pod has finished to terminate it.

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

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

  • RERC resources must have a unique name (RED-96302) The string "rec-name"/"rec-namespace" must be different from all other participating clusters in the 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 controller only supports global database options. Configuration specific to location is not supported (RED-86490)

  • 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 (R...

Read more
Assets 2

7.4.2-2

15 Feb 20:17
@bascar bascar
v7.4.2-2
93049bb
This commit was created on GitHub.com and signed with GitHub’s verified signature.
GPG key ID: B5690EEEBB952194
Learn about vigilant mode.
Compare
Choose a tag to compare
7.4.2-2

Highlights

The primary purpose of this release is to support Redis Enterprise 7.4.2, which is a major update to Redis Enterprise Software. As such, we have limited the scope of changes to focus on supporting RS 7.4 changes, in addition to implementing a few enhancements and major fixes.

New in this release

Enhancements

  • Added RESP3 support in K8s APIs (RED-94601)
  • Added to supported distributions
  • Added support for Redis Enterprise Software 7.4.2
  • Enhanced resilience of operators to misconfigured REDB namespaces (RED-113908)
  • Both the operator and services rigger are now based on UBI9 (RED-116083)

Resolved issues

  • Fixed the operator to prevent reconciliation of non-REDB custom resources in observed namespaces. This eliminates the need for unnecessary permission rules. (RED-87790)
  • Fixed excessive updates to ingresses and services. (RED-109289)
  • Fixed update issues in rigger after the upgrade in multi-namespace environments. (RED-111732)
  • Fixed Active-Active sharding configuration by adding a new field. (RED-112909)
  • Fixed operator CVE. (RED-115157)
  • Fixed a race condition that could have rarely caused the cluster upgrade to break. (RED-118940)

API changes

CRD Field Change Description
REC resp3Default Add Boolean controlling whether Resp3 should be enabled by default
REDB resp3 Add Controls resp3 for specific REDBs

Version changes

Breaking changes

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

Upgrade operating system

If your databases use modules, you need to update all nodes in the cluster to Redis Enterprise 7.2.4 or later before upgrading your operating system. See Upgrade a cluster's operating systemin the Redis Enterprise Software documentation for more details.

terminationGracePeriodSeconds

The configurable terminationGracePeriodSeconds REC field was added in version 7.2.4-12 to replace the hard-coded timeout of 15 minutes for a node to be stopped or drained (RED-111471).

ValidatingWebhookConfiguration

Versions 6.4.2-4 and later include 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

Versions 6.4.2-6 and later include 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 instructions.

Deprecations

  • Redis Software for Kubernetes no longer supports the RHEL7 operating system. Migrate to RHEL8 to use this version.

Supported distributions

The following table shows supported distributions at the time of this release. You can also find this list in Supported Kubernetes distributions.

✅ Supported – This distribution is supported for this version of Redis Enterprise Software for Kubernetes.

⚠️ Deprecated – This distribution is still supported for this version of Redis Enterprise Software for Kubernetes, but support will be removed in a future release.

❌ End of life – Support for this distribution ended.

Any distribution not listed below is not supported for production workloads.

Kubernetes version 1.24 1.25 1.26 1.27 1.28 1.29
Community Kubernetes ❌ ❌ ⚠️ ✅ ✅ ✅
Amazon EKS ⚠️ ⚠️ ✅ ✅ ✅
Azure AKS ❌ ❌ ⚠️ ✅ ✅
Google GKE ❌ ⚠️ ✅ ✅ ✅
Rancher RKE2 ⚠️ ✅ ✅ ✅
VMware TKG 2.2 ⚠️ ⚠️
VMware TKG 2.3 ✅ ✅ ✅
VMware TKG 2.4 ✅ ✅ ✅
OpenShift version 4.11 4.12 4.13 4.14
⚠️ ⚠️ ✅ ✅
VMware TKGI version 1.15 1.16 1.17 1.18
✅ ✅ ✅ ✅

Downloads

  • Redis Enterprise: redislabs/redis:7.4.2-54
  • Operator: redislabs/operator:7.4.2-2
  • Services Rigger: redislabs/k8s-controller:7.4.2-2

OpenShift images

  • Redis Enterprise: registry.connect.redhat.com/redislabs/redis-enterprise:7.4.2-54.rhel8-openshift
  • Operator: registry.connect.redhat.com/redislabs/redis-enterprise-operator:7.4.2-2
  • Services Rigger: registry.connect.redhat.com/redislabs/services-manager:7.4.2-2

OLM bundle

Redis Enterprise operator bundle : v7.4.2-2

Known limitations

The limitations below are specific to the Redis Enterprise for Kubernetes product. To view limitations for the supported Redis Enterprise Software version, see the 7.4.2 release notes.

New limitations

  • The REDB “redisVersion” field can’t be used for memcached databases(RED-119152)

Existing limitations

  • When modifying the database suffix for an Active-Active database, while the service-rigger is in a terminating state, the services-rigger will delete and create the ingress or route resources in a loop (RED-107687) Wait until the services- rigger pod has finished to terminate it.

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

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

  • RERC resources must have a unique name (RED-96302) The string "rec-name"/"rec-namespace" must be different from all other participating clusters in the 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 controller only supports global database options. Configuration specific to location is not supported (RED-86490)

  • 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 cluste...

Read more
Assets 2

7.2.4-12

14 Dec 19:50
@bascar bascar
v7.2.4-12
86513c1
This commit was created on GitHub.com and signed with GitHub’s verified signature. The key has expired.
GPG key ID: 4AEE18F83AFDEB23
Expired
Learn about vigilant mode.
Compare
Choose a tag to compare
7.2.4-12

Highlights

This is a maintenance release with a few enhancements/fixes on the Kubernetes product and a newer Redis Enterprise container version.

New in this release

Enhancements

  • Added to supported distributions
  • Added support for Redis Enterprise Software 7.2.4-92 (RED-113750)
  • Replaced usage of config maps for readiness check and prestop scripts of Redis Enterprise pods (RED-81443)

Resolved issues

  • Fixed issues around REC creation when namespace contains old resources from previous installation (RED-100669) (RED-100668)
  • Fixed constant updates to watched namespaces REDB services (RED-103264)
  • Fixed labeling of old operator configmaps (RED-105517)
  • Removed automatic upgrades of modules during upgrades (RED-106834)
  • Fixed unexpected restart of container during cluster recovery (RED-108511)
  • Fixed timeout of prestop (RED-111471)
  • Fixed deployment issues on TKG (RED-111271)

Version changes

Breaking changes

The following changes included in this release affect the upgrade process. Please read carefully before upgrading to 7.2.4-12.

Upgrade operating system

{{}}If your databases use modules, you need to update all nodes in the cluster to Redis Enterprise 7.2.4 or later before upgrading your operating system. See Upgrade a cluster's operating system in the Redis Enterprise Software documentation for more details.{{}}

terminationGracePeriodSeconds

The configurable terminationGracePeriodSeconds REC field has been added to replace the hard-coded timeout of 15 minutes for a node to be stopped/drained (RED-111471).

ValidatingWebhookConfiguration

Versions 6.4.2-4 and later include 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

Versions 6.4.2-6 and later include 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 instructions.

Upcoming changes

  • A future release of Redis Enterprise will remove support for RHEL7. We recommend migrating to RHEL8.

Supported distributions

The following table shows supported distributions at the time of this release. You can also find this list in Supported Kubernetes distributions
✅ Supported – This distribution is supported for this version of Redis Enterprise Software for Kubernetes.

⚠️ Deprecated – This distribution is still supported for this version of Redis Enterprise Software for Kubernetes, but support will be removed in a future release.

❌ End of life – Support for this distribution ended.

Any distribution not listed below is not supported for production workloads.

Kubernetes version 1.23 1.24 1.25 1.26 1.27 1.28
Community Kubernetes ✅ ✅ ✅ ✅ ✅
Amazon EKS ⚠️ ✅ ✅ ✅ ✅
Azure AKS ✅ ✅ ✅ ✅
Google GKE ❌ ✅ ✅ ✅ ✅ ✅
Rancher 2.6 ❌ ❌
Rancher RKE2 ⚠️ ✅ ✅ ✅
VMware TKG 2.1 ⚠️ ✅
VMware TKG 2.2 ✅ ✅ ✅
VMware TKG 2.3 ✅ ✅ ✅
OpenShift version 4.10 4.11 4.12 4.13 4.14
❌ ✅ ✅ ✅ ✅
VMware TKGI version 1.14 1.15
❌ ✅

Downloads

  • Redis Enterprise: redislabs/redis:7.2.4-92
  • Operator: redislabs/operator:7.2.4-12
  • Services Rigger: redislabs/k8s-controller:7.2.4-12.

OpenShift images

  • Redis Enterprise: registry.connect.redhat.com/redislabs/redis-enterprise:7.2.4-92.rhel8-openshift
    (or redislabs/redis-enterprise:7.2.4-92.rhel7-openshift if upgrading from RHEL 7)
  • Operator: registry.connect.redhat.com/redislabs/redis-enterprise-operator:7.2.4-12
  • Services Rigger: registry.connect.redhat.com/redislabs/services-manager:7.2.4-12

OLM bundle

Redis Enterprise operator bundle : v7.2.4-12

Known limitations

The limitations below are specific to the Redis Enterprise for Kubernetes product. To view limitations for the supported Redis Enterprise Software version, see the 7.2.4 release notes.

Existing limitations

  • When modifying the database suffix for an Active-Active database, while the service-rigger is in a terminating state, the services-rigger will delete and create the ingress or route resources in a loop (RED-107687) Wait until the services- rigger pod has finished to terminate it.

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

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

  • RERC resources must have a unique name (RED-96302) The string "rec-name"/"rec-namespace" must be different from all other participating clusters in the 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 controller only supports global database options. Configuration specific to location is not supported (RED-86490)

  • 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 t...

Read more
Assets 2

7.2.4-7

03 Oct 15:22
@bascar bascar
v7.2.4-7
1cdfab5
This commit was created on GitHub.com and signed with GitHub’s verified signature. The key has expired.
GPG key ID: 4AEE18F83AFDEB23
Expired
Learn about vigilant mode.
Compare
Choose a tag to compare
7.2.4-7

Highlights

This is a minor maintenance release with a few enhancement/fixes on the Kubernetes product, and a newer Redis Enterprise container version.

The following are the notable changes:

  • Customers who are on RHEL 7 based images and who are already using this version of 7.2 can migrate to RHEL 8 based images when they upgrade.
    • Previously, you could not migrate a cluster to newer OS version.
    • All customers should plan to move to RHEL 8 based images. The next major version of Redis Enterprise will not support RHEL 7.
  • Added VMware TKG 2.1 and 2.2 to the Supported distributions table.

New in this release

Enhancements

  • Support for migration from RHEL7 images to RHEL8 during upgrade (RED-106785)
  • Support for Redis Enterprise Software version 7.2.4-64 (RED-108832)

Resolved issues

  • Fixed cluster recovery flow when non default modules are used (RED-107711 RED-106872)

Version changes

Breaking changes

The following changes included in this release affect the upgrade process. Please read carefully before upgrading to 7.2.4-7.

ValidatingWebhookConfiguration

Versions 6.4.2-4 and later include 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

Versions 6.4.2-6 and later include 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 instructions.

Upcoming changes

  • A future release of Redis Enterprise will remove support for RHEL7. We recommend migrating to RHEL8.

Supported distributions

The following table shows supported distributions at the time of this release. You can also find this list in Supported Kubernetes distributions.

✅ Supported – This distribution is supported for this version of Redis Enterprise Software for Kubernetes.

⚠️ Deprecated – This distribution is still supported for this version of Redis Enterprise Software for Kubernetes, but support will be removed in a future release.

❌ End of life – Support for this distribution ended.

Any distribution not listed below is not supported for production workloads.

Kubernetes version 1.22 1.23 1.24 1.25 1.26 1.27
Community Kubernetes ❌ ❌ ✅ ✅ ✅ ✅
Amazon EKS ❌ ⚠️ ✅ ✅ ✅ ✅
Azure AKS ❌ ❌ ✅ ✅ ✅
Google GKE ❌ ⚠️ ✅ ✅ ✅ ✅
Rancher 2.6 ❌ ❌ ⚠️
Rancher 2.7 ⚠️ ✅ ✅
VMware TKG 1.6 ⚠️ ⚠️
VMware TKG 2.1 ⚠️ ⚠️ ✅
VMware TKG 2.2 ✅ ✅ ✅
OpenShift version 4.9 4.10 4.11 4.12 4.13
❌ ⚠️ ✅ ✅ ✅
VMware TKGI version 1.13 1.14 1.15 1.16
❌ ⚠️ ✅ ✅

Downloads

  • Redis Enterprise: redislabs/redis:7.2.4-64
  • Operator: redislabs/operator:7.2.4-7
  • Services Rigger: redislabs/k8s-controller:7.2.4-7.

OpenShift images

  • Redis Enterprise: registry.connect.redhat.com/redislabs/redis-enterprise:7.2.4-64.rhel8-openshift
    (or redislabs/redis-enterprise:7.2.4-64.rhel7-openshift if upgrading from RHEL 7)
  • Operator: registry.connect.redhat.com/redislabs/redis-enterprise-operator:7.2.4-7
  • Services Rigger: registry.connect.redhat.com/redislabs/services-manager:7.2.4-7

OLM bundle

Redis Enterprise operator bundle : v7.2.4-7

Known limitations

The limitations below are specific to the Redis Enterprise for Kubernetes product. To view limitations for the supported Redis Enterprise Software version, see the 7.2.4 release notes.

Existing limitations

  • REDBs created with versions before 6.2.10-4 will automatically upgrade modules when the cluster is upgraded (RED-106834)

  • When modifying the database suffix for an Active-Active database, while the service-rigger is in a terminating state, the services-rigger will detele and create the ingress or route resources in a loop (RED-107687) Wait until the services- rigger pod has finished to terminate it.

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

  • RERC resources must have a unique name (RED-96302) The string "rec-name"/"rec-namespace" must be different from all other participating clusters in the 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 controller only supports global database options. Configuration specific to location is not supported (RED-86490)

  • 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 pro...

Read more
Assets 2

7.2.4-2

22 Aug 15:12
@bascar bascar
v7.2.4-2
d4878a8
This commit was created on GitHub.com and signed with GitHub’s verified signature. The key has expired.
GPG key ID: 4AEE18F83AFDEB23
Expired
Learn about vigilant mode.
Compare
Choose a tag to compare
7.2.4-2

Highlights

The primary purpose this release is supporting Redis Enterprise 7.2.4, which is a major Redis Enterprise Software update. As such, we reduced the scope of changes to support the underlying change of RS 7.2 and a few significant fixes.

The following are the notable changes:

  • Support for Redis Enterprise 7.2.4

  • New default engine, Speedb, for Auto Tiering (formerly Redis on Flash)

  • Changes to supported Kubernetes distributions

New in this release

Enhancements

  • Support for Redis Enterprise 7.2.4 (RED-73681)
  • New default engine, Speedb, for Auto Tiering (formerly Redis on Flash) (RED-90850)
  • Security context hardening (RED-98447)

Resolved issues

  • Fixed: Services or routes from the Active-Active setup might not be removed (RED-77752)
  • Fixed: Admission controller may not alert when patching the REAADB with missing secret or RERC (RED-104463)

API changes

The following fields were added to the RedisEnterpriseCluster (REC) custom resource definition (CRD):

  • Added status.BundledDatabaseRedisVersions.major as a Boolean field indicating whether the Redis version is major.
  • Added spec.RedisOnFlashSpec.bigStoreDriver to indicate the storage engine used for Auto Tiering (formerly Redis on Flash).

Version changes

Breaking changes

The following changes included in this release affect the upgrade process. Please read carefully before upgrading to 7.2.4-2.

ValidatingWebhookConfiguration

Versions 6.4.2-4 and later include 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

Versions 6.4.2-6 and later include 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 instructions.

Deprecations

  • Gesher (advanced admission control configuration support) previously deprecated, is no longer supported.
  • Deprecated spec.RedisOnFlashSpec.flashStorageEngine field for the RedisEnterpriseCluster. Use bigStoreDriver field to indicate storage engines going forward.

Supported distributions

The following table shows supported distributions at the time of this release. You can also find this list in Supported Kubernetes distributions.

✅ Supported – This distribution is supported for this version of Redis Enterprise Software for Kubernetes.

⚠️ Deprecated – This distribution is still supported for this version of Redis Enterprise Software for Kubernetes, but support will be removed in a future release.

❌ End of life – Support for this distribution ended.

Any distribution not listed below is not supported for production workloads.

Kubernetes version 1.22 1.23 1.24 1.25 1.26 1.27
Community Kubernetes ❌ ❌ ✅ ✅ ✅ ✅
Amazon EKS ❌ ⚠️ ✅ ✅ ✅ ✅
Azure AKS ❌ ❌ ✅ ✅ ✅
Google GKE ❌ ⚠️ ✅ ✅ ✅ ✅
Rancher 2.6 ❌ ❌ ⚠️
Rancher 2.7 ⚠️ ✅ ✅
VMware TKG 1.6 ⚠️ ⚠️
VMware TKG 2.1 ⚠️ ⚠️ ✅
VMware TKG 2.2 ✅ ✅ ✅
OpenShift version 4.9 4.10 4.11 4.12 4.13
❌ ⚠️ ✅ ✅ ✅
VMware TKGI version 1.13 1.14 1.15 1.16
❌ ⚠️ ✅ ✅

Downloads

  • Redis Enterprise: redislabs/redis:7.2.4-52
  • Operator: redislabs/operator:7.2.4-2
  • Services Rigger: redislabs/k8s-controller:7.2.4-2.

OpenShift images

  • Redis Enterprise: registry.connect.redhat.com/redislabs/redis-enterprise:7.2.4-52.rhel8-openshift
    (or redislabs/redis-enterprise:7.2.4-52.rhel7-openshift if upgrading from RHEL 7)
  • Operator: registry.connect.redhat.com/redislabs/redis-enterprise-operator:7.2.4-2
  • Services Rigger: registry.connect.redhat.com/redislabs/services-manager:7.2.4-2

OLM bundle

Redis Enterprise operator bundle : v7.2.4-2

{{}}
For users of Red Hat’s OLM installer, Redis is working with Red Hat on an upload issue that prevents the listing of this release in their OLM system. We will update any status or changes here. If this message is missing, then the issue has been resolved.
{{}}

Known limitations

The limitations below are specific to the Redis Enterprise for Kubernetes product. To view limitations for the supported Redis Enterprise Software version, see the 7.2.4 release notes.

New limitations

  • Cannot upgrade or recover clusters if there are databases with modules that aren't built in (RED-107711 RED-106872) Contact support to upload your modules manually.

  • When modifying the database suffix for an Active-Active database, while the service-rigger is in a terminating state, the services-rigger will detele and create the ingress or route resources in a loop (RED-107687) Wait until the services- rigger pod has finished to terminate it.

Existing limitations

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

  • RERC resources must have a unique name (RED-96302) The string "rec-name"/"rec-namespace" must be different from all other participating clusters in the 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 controller only supports global database options. Configuration specific to location is not supported (RED-86490)

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

Read more
Assets 2

6.4.2-8

27 Jul 14:30
@yuvallevy2 yuvallevy2
v6.4.2-8
a4def4a
This commit was created on GitHub.com and signed with GitHub’s verified signature. The key has expired.
GPG key ID: 4AEE18F83AFDEB23
Expired
Learn about vigilant mode.
Compare
Choose a tag to compare
6.4.2-8

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

  • 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 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

This release doesn't introduce any new known limitations. See section below for existing known limitations.

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.

Assets 2

6.4.2-6

22 Jun 18:29
@bascar bascar
v6.4.2-6
25d6f03
This commit was created on GitHub.com and signed with GitHub’s verified signature. The key has expired.
GPG key ID: 4AEE18F83AFDEB23
Expired
Learn about vigilant mode.
Compare
Choose a tag to compare
6.4.2-6

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-6s
  • 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:

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

Note: 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

  • 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]({{<relref "/kubernetes/deployment/quick-start.md">}}).

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

  • **...

Read more
Assets 2

6.4.2-5

19 Apr 18:19
@bascar bascar
v6.4.2-5
2fad9a7
This commit was created on GitHub.com and signed with GitHub’s verified signature. The key has expired.
GPG key ID: 4AEE18F83AFDEB23
Expired
Learn about vigilant mode.
Compare
Choose a tag to compare
6.4.2-5

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

Upgrade to 6.4.2-4

This release uses a new ValidatingWebhookConfiguration resource that replaces the old webhook resource. To use the 6.4.2-5 release, delete the old webhook resource and apply the new file.

  1. Delete the existing ValidatingWebhookConfiguration on the Kubernetes cluster (named redb-admission).

    kubectl delete ValidatingWebhookConfiguration redb-admission

  2. Apply the resource from the new file.

    kubectl apply -f deploy/admission/webhook.yaml

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

Known limitations

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

Assets 2

6.4.2-4

13 Mar 20:59
@bascar bascar
v6.4.2-4
0575f5a
Compare
Choose a tag to compare
6.4.2-4

Overview

The Redis Enterprise K8s 6.4.2-4 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-43
  • Operator: redislabs/operator:6.4.2-4
  • Services Rigger: redislabs/k8s-controller:6.4.2-4

OpenShift images

  • Redis Enterprise: registry.connect.redhat.com/redislabs/redis-enterprise:6.4.2-43.rhel8-openshift
    (or redislabs/redis-enterprise:6.4.2-43.rhel7-openshift if upgrading from RHEL 7)
  • Operator: registry.connect.redhat.com/redislabs/redis-enterprise-operator:6.4.2-4s
  • Services Rigger: registry.connect.redhat.com/redislabs/services-manager:6.4.2-4

OpenShift OLM bundles

  • Redis Enterprise operator bundle version: v6.4.2-4.0

Upgrade to 6.4.2-4

This release uses a new ValidatingWebhookConfiguration resource that replaces the old webhook resource. To use the 6.4.2-4 release, delete the old webhook resource and apply the new file.

  1. Delete the existing ValidatingWebhookConfiguration on the Kubernetes cluster (named redb-admission).

    kubectl delete ValidatingWebhookConfiguration redb-admission

  2. Apply the resource from the new file.

    kubectl apply -f deploy/admission/webhook.yaml

New features

  • Cluster-level LDAP configuration support in REC (RED-83533)
  • Public preview support for declarative Active-Active configuration (RED-86470)(RED-86470)

Feature improvements

  • New labeling method for multi-namespace REDB (RED-83102)
  • Operator deployment uses built-in SCC in OpenShift (RED-90524)
  • Support for Redis Enterprise 6.4.2-43
  • Support added for K8s 1.26, EKS 1.24, AKS 1.25, Rancher 2.7/1.23-24
  • Improved log collector display and error handling

Bug fixes

API changes

The following fields were changed in the Redis Enterprise cluster (REC) API:

  • Added .spec.ldap for configuring cluster-level LDAP settings

  • Added .spec.certificates.ldapClientCertificateSecretName for configuring LDAP client certificate

  • Added .status.managedAPIs to track APIs managed by the operator

  • The following custom resources definitions were added:

    • RedisEnterpriseRemoteCluster (RERC)
    • RedisEnterpriseActiveActiveDatabase (REAADB)

Compatibility notes

Deprecated features

  • Support for Gesher, the advanced admission control configuration, is deprecated.
  • The app.redislabs.com/v1alpha1 API version of the RedisEnterpriseCluster (REC) custom resource is deprecated and will be removed in a subsequent release. Customers should switch to use the app.redislabs.com/v1 API version instead.

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.21 1.22 1.23 1.24 1.25 1.26
Community Kubernetes deprecated supported supported supported supported*
Amazon EKS supported supported supported*
Azure AKS deprecated supported supported*
Google GKE supported supported supported supported
Rancher 2.6 deprecated supported supported supported
Rancher 2.7 supported* supported*
VMware TKG 1.6 supported supported
OpenShift version 4.8 4.9 4.10 4.11 4.12
deprecated deprecated supported supported supported*
VMware TKGI version 1.12 1.13 1.14 1.15
deprecated supported supported

* Support added in this release

Active-Active preview known limitations

  • No support for Hashicorp Vault for storing secrets (RED-95805)

  • No module support (RED-95153)

  • No support for client certificates in secrets (RED-95724)

  • No support for backup configuration (RED-95724)

  • No support for upgrading the database Redis version

  • REAADB secret status isn't updated in source cluster (RED-96296)

    The workaround is to view the secret status in one of the remote clusters.

  • Invalid REAADB is not rejected by admission might get deleted after apply. (RED-96300)

    Fix the problems with the REAADB and reapply. Contact support if you aren't sure why the REAADB is invalid.

  • Admission is not blocking REAADB with shardCount which exceeds license quota. (RED-96301)

    Fix the problems with the REAADB and reapply.

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

  • Only global database options are supported, not support for specifying configuration per location.

  • Can't automatically update the cluster secret via the operator (can be updated manually).

  • No support for migration from old (manual) Active-Active database method to new Active-Active controller.

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

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

    When a cluster is in unreachable state, the state remains running instead of triggering 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 reported node CPU usage 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 (namely, "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 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.

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

  • autoUpgrade set to true can cause unexpected bdb upgrades when redisUpgradePolicy is set to true (RED-72351)

    Contact support if your deployment is impacted.

Assets 2

6.2.18-41

22 Dec 08:52
@yuvallevy2 yuvallevy2
v6.2.18-41
da037dc
This commit was created on GitHub.com and signed with GitHub’s verified signature. The key has expired.
GPG key ID: 4AEE18F83AFDEB23
Expired
Learn about vigilant mode.
Compare
Choose a tag to compare
6.2.18-41

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.

Images

This release includes the following container images:

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

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

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.

  • 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]({{<relref "/kubernetes/deployment/quick-start.md">}}) 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.

Assets 2