Skip to content

Commit 8111ac1

Browse files
kaitlynmichaelkaitlynmichael
committed
release notes
1 parent 897ecc7 commit 8111ac1

File tree

2 files changed

+169
-0
lines changed

2 files changed

+169
-0
lines changed

‎content/operate/kubernetes/release-notes/7-8-6-releases/7-8-6-1-march2025.md‎

Lines changed: 91 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,91 @@
1+
---
2+
alwaysopen: false
3+
categories:
4+
- docs
5+
- operate
6+
- kubernetes
7+
description: Feature release including enhancements, bug fixes, platform updates, and support for Redis Software 7.8.6-13
8+
hideListLinks: true
9+
linkTitle: 7.8.6-1 (March 2025)
10+
title: Redis Enterprise for Kubernetes 7.8.6-1 (March 2025) release notes
11+
weight: 50
12+
---
13+
14+
## New in the release
15+
16+
Redis Enterprise for Kubernetes 7.8.6-1 is a feature release that includes enhancements, bug fixes, platform updates, and support for Redis Software 7.8.6-13.
17+
18+
### Enhancements
19+
20+
- Added support for Redis Software 7.8.6-13.
21+
- Updated supported Kubernetes distributions
22+
- DatabaseServicePortPolicy allows use of the default Redis port (6379) for database services.
23+
- Added additional license fields to the REC status.
24+
- Added validation to prevent unsupported changes to podDisruptionBudget.
25+
26+
### Resolved issues
27+
28+
- Removed unnecessary users from the Redis Enterprise container image (RED-73626).
29+
- Fixed Sonarcube findings in the log collector (RED-129297).
30+
- Fixed upgrade failure due to update of the nodeSelector during the upgrade (RED-138445).
31+
- Fixed issues with Vault plugin connections to Redis Enterprise (RED-139352 RED-144637).
32+
- Fixed operator crash when a namespace is labeled with a specific label (RED-140344).
33+
- Fixed failure in Services Rigger when a database uses port 10250 (RED-142673).
34+
- Reduced CPU priority of the health_check.py script to ensure availability (RED-144360).
35+
- Fixed broken use case for customizing the Active-Active port. (RED-149374).
36+
- Fixed API reference for REDB properties (RED-151195).
37+
- Fixed operator CVE-2024-24786 (RED-151873).
38+
- Fixed wrong image tag for OpenShift example YAML (RED-152022).
39+
40+
### API changes
41+
42+
| **CRD** | **Field** | **Change** | **Description** |
43+
|---|---|---|---|
44+
| REAADB | `spec.externalReplicationPort` | ADD | Specifies the replication endpoint port number for users who use LoadBalancers to synchronize Active-Active replicas and must provide the port that the LoadBalancer listens on. |
45+
| REC | `status.shardsUsage` | ADD | Total number of shards (both RAM and flash) currently in use under this license. |
46+
| REC | `status.flashShards` | ADD | Number of flash shards currently in use under this license. |
47+
| REC | `status.flashShardsLimit` | ADD | Number of flash shards allowed under this license. |
48+
| REC | `status.ramShards` | ADD | Number of RAM shards currently in use under this license. |
49+
| REC | `status.ramShardsLimit` | ADD | Number of RAM shards allowed under this license. |
50+
| REC | `spec.podSecurityPolicyName` | REMOVE | Not supported anymore by supported Kubernetes versions. |
51+
| REC | `spec.databaseServicePortPolicy` | ADD | Specifies how to determine service ports for REDB services. Defaults to DatabasePortForward if not set. DatabasePortForward - The service port will be the same as the database port. RedisDefaultPort - The service port will be the default Redis port (6379).
52+
53+
## Breaking changes
54+
55+
Customers who use load balancers for Active-Active replication endpoints and rely on the change introduced in RED-113626 (or the workaround described in the ticket) must set the spec.externalReplicationPort field in REAADB after upgrading. Otherwise, replication will fail (RED-149374).
56+
57+
## Supported distributions
58+
59+
The following table shows supported distributions at the time of this release. You can also find this list in [Supported Kubernetes distributions]({{< relref "/operate/kubernetes/reference/supported_k8s_distributions" >}}).
60+
61+
<span title="Check mark icon">&#x2705;</span> Supported – This distribution is supported for this version of Redis Enterprise Software for Kubernetes.
62+
63+
<span title="Deprecation warning" class="font-serif">:warning:</span> Deprecated – This distribution is still supported for this version of Redis Enterprise Software for Kubernetes, but support will be removed in a future release.
64+
65+
<span title="X icon">&#x274c;</span> End of life – Support for this distribution ended.
66+
67+
Any distribution not listed below is not supported for production workloads.
68+
69+
| Kubernetes version | **1.26** | **1.27** | **1.28** | **1.29** | **1.30** | **1.31** | **1.32** |
70+
|---|---|---|---|---|---|---|---|
71+
| **Community K8s** | | | <span title="X icon">&#x274c;</span> | <span title="X icon">&#x274c;</span> | <span title="Supported">&#x2705;</span> | <span title="Supported">&#x2705;</span> | <span title="Supported">&#x2705;</span> |
72+
| **Amazon EKS** | | | <span title="X icon">&#x274c;</span> | <span title="Deprecation warning" class="font-serif">:warning:</span> | <span title="Supported">&#x2705;</span> | <span title="Supported">&#x2705;</span> | <span title="Supported">&#x2705;</span> |
73+
| **Azure EKS** | | | <span title="X icon">&#x274c;</span> | <span title="Deprecation warning" class="font-serif">:warning:</span> | <span title="Supported">&#x2705;</span> | <span title="Supported">&#x2705;</span> | <span title="Supported">&#x2705;</span> |
74+
| **Google GKE** | | | <span title="X icon">&#x274c;</span> | <span title="Deprecation warning" class="font-serif">:warning:</span> | <span title="Supported">&#x2705;</span> | <span title="Supported">&#x2705;</span> | <span title="Supported">&#x2705;</span> |
75+
| **Rancher** | | <span title="X icon">&#x274c;</span> | <span title="Supported">&#x2705;</span> | <span title="Supported">&#x2705;</span> | <span title="Supported">&#x2705;</span> | | |
76+
| **VMware TKG 2.4** | <span title="Deprecation warning" class="font-serif">:warning:</span> | <span title="Deprecation warning" class="font-serif">:warning:</span> | | | | | |
77+
| **OpenShift** | **4.13** | **4.14** | **4.15** | **4.16** | **4.17** | **4.18** | |
78+
| | <span title="Deprecation warning" class="font-serif">:warning:</span> | <span title="Deprecation warning" class="font-serif">:warning:</span> | <span title="Supported">&#x2705;</span> | <span title="Supported">&#x2705;</span> | <span title="Supported">&#x2705;</span> | | |
79+
| **VMware TKGI** | **1.16 | **1.17 | **1.18 | **1.19 | **1.2 | | |
80+
| | | <span title="Deprecation warning" class="font-serif">:warning:</span> | <span title="Deprecation warning" class="font-serif">:warning:</span> | <span title="Supported">&#x2705;</span> | <span title="Supported">&#x2705;</span> | | |
81+
82+
## Downloads
83+
84+
- **Redis Enterprise**: `redislabs/redis:7.8.6-1`
85+
- **Operator**: `redislabs/operator:7.8.6-13`
86+
- **Services Rigger**: `redislabs/k8s-controller:7.8.6-1`
87+
- **OLM operator bundle** : `v7.8.6-1.0`
88+
89+
## Known limitations
90+
91+
See [7.8.6 releases]({{<relref "release-notes/7-8-6-releases">}}) for information on known limitations.

‎content/operate/kubernetes/release-notes/7-8-6-releases/_index.md‎

Lines changed: 78 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,78 @@
1+
---
2+
alwaysopen: false
3+
categories:
4+
- docs
5+
- operate
6+
- kubernetes
7+
description: Releases with support for Redis Enterprise Software 7.8.4
8+
hideListLinks: true
9+
linkTitle: 7.8.4 releases
10+
title: Redis Enterprise for Kubernetes 7.8.4 release notes
11+
weight: 47
12+
---
13+
14+
Redis Enterprise for Kubernetes 7.8.6-1 includes bug fixes, enhancements, and support for Redis Enterprise Software version 7.8.6-13 .
15+
16+
## Detailed release notes
17+
18+
{{<table-children columnNames="Version&nbsp;(Release&nbsp;date)&nbsp;,Major changes" columnSources="LinkTitle,Description" enableLinks="LinkTitle">}}
19+
20+
## Breaking changes
21+
22+
Customers who use load balancers for Active-Active replication endpoints and rely on the change introduced in RED-113626 (or the workaround described in the ticket) must set the spec.externalReplicationPort field in REAADB after upgrading. Otherwise, replication will fail (RED-149374).
23+
24+
## Known limitations
25+
26+
- **Only upgrades from 7.4.2-2 and later are supported.** If you are using an earlier version, install 7.4.2-2 before upgrading to 7.8.2-6 or later.
27+
28+
- **When changing the REDB field `spec.modulesList`, version might be upgraded to latest, even if a different version is specified.** To prevent the upgrade to latest, set `spec.upgradeSpec.setModuleToLatest` to `false` before upgrading to 7.8.2-6.
29+
30+
- **Missing endpoint for admission endpoint (rare) (RED-119469)** Restart the operator pod.
31+
32+
- **The REDB “redisVersion” field can’t be used for memcached databases(RED-119152)**
33+
34+
- **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.
35+
36+
- **REAADB changes might fail with "gateway timeout" errors, mostly on OpenShift (RED-103048)** Retry the operation.
37+
38+
- **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.
39+
40+
- **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.
41+
42+
- **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.
43+
44+
- **Admission is not blocking REAADB with `shardCount` which exceeds license quota (RED-96301)** Fix the problems with the REAADB and reapply.
45+
46+
- **Active-Active controller only supports global database options. Configuration specific to location is not supported (RED-86490)**
47+
48+
- **Active-Active setup removal might keep services or routes undeleted (RED-77752)** Delete services or routes manually if you encounter this problem.
49+
50+
- **`autoUpgrade` set to `true` can cause unexpected bdb upgrades when `redisUpgradePolicy` is set to `true` (RED-72351)** Contact support if your deployment is impacted.
51+
52+
- **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.
53+
54+
- **PVC size issues when using decimal value in spec (RED-62132)** Make sure you use integer values for the PVC size.
55+
56+
- **REC might report error states on initial startup (RED-61707)** There is no workaround at this time except to ignore the errors.
57+
58+
- **Hashicorp Vault integration - no support for Gesher (RED-55080)** There is no workaround for this issue. Gesher support has been deprecated.
59+
60+
- **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.
61+
62+
- **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.
63+
64+
- **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".
65+
66+
- **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.
67+
68+
- **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.
69+
70+
- **K8s-based 5.4.10 clusters seem to negatively affect existing 5.4.6 clusters (RED-37233)** Upgrade clusters to latest version.
71+
72+
- **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.
73+
74+
- **An unreachable cluster has status running (RED-32805)** When a cluster is in an unreachable state, the state remains `running` instead of triggering an error.
75+
76+
- **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.
77+
78+
- **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.

0 commit comments

Comments
 (0)