Skip to content

Commit 0498e08

Browse files
kaitlynmichaelkaitlynmichael
authored
K8s 6.2.12-1 release notes (RedisLabs#2144)
* 6.2.12 draft release notes * new bug fix
1 parent 331bb75 commit 0498e08

File tree

2 files changed

+175
-1
lines changed

2 files changed

+175
-1
lines changed

‎content/kubernetes/release-notes/k8s-6-2-10-45-2022-07.md

Lines changed: 5 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1,5 +1,5 @@
11
---
2-
Title: Redis Enterprise for Kubernetes Release Notes 6.2.10-45 (July 2022)
2+
Title: Redis Enterprise for Kubernetes release notes 6.2.10-45 (July 2022)
33
linktitle: 6.2.10-45 (July 2022)
44
description: Support added for additional distributions as well as some feature improvements.
55
weight: 62
@@ -99,6 +99,10 @@ Below is a table showing supported distributions at the time of this release. Se
9999

100100
The `redis-enterprise-operator` role is missing permission on replica sets.
101101

102+
* Private registries are not supported on OpenShift 3.11 (RED-38579)
103+
104+
OpenShift 3.11 does not support DockerHub private registries. This is a known OpenShift issue.
105+
102106
* Internal DNS and Kubernetes DNS may have conflicts (RED-37462)
103107

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

‎content/kubernetes/release-notes/k8s-6-2-12-1.md

Lines changed: 170 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,170 @@
1+
---
2+
Title: Redis Enterprise for Kubernetes release notes 6.2.12-1 (Sept 2022)
3+
linktitle: 6.2.12-1 (Sept 2022)
4+
description: Support added for additional distributions, as well as feature improvements and bug fixes.
5+
weight: 61
6+
alwaysopen: false
7+
categories: ["Platforms"]
8+
aliases: [
9+
/kubernetes/release-notes/k8s-6-2-12-1.md,
10+
/kubernetes/release-notes/k8s-6-2-12-1/, ]
11+
---
12+
## Overview
13+
14+
The Redis Enterprise K8s 6.2.12-1 supports the Redis Enterprise Software release 6.2.12 and includes feature improvements and bug fixes.
15+
16+
The key bug fixes and known limitations are described below.
17+
18+
## Images
19+
20+
This release includes the following container images:
21+
22+
* **Redis Enterprise**: `redislabs/redis:6.2.12-82` or `redislabs/redis:6.2.12-82.rhel8-openshift`
23+
* **Operator**: `redislabs/operator:6.2.12-1`
24+
* **Services Rigger**: `redislabs/k8s-controller:6.2.12-1` or `redislabs/services-manager:6.2.12-1` (on the Red Hat registry)
25+
26+
## Feature improvements
27+
28+
* Redis Enterprise Software 6.2.12 support (RED-83829)
29+
* Added support for annotations on services created by Redis Enterprise (RED-56245)
30+
* Support for additional builds of same Redis Software version with same operator version. The list of supported builds will be published. (RED-78757)
31+
32+
33+
## Bug fixes
34+
35+
* Fixed Golang related vulnerabilities (RED-79205)
36+
* Log collector creating larger packages (RED-79650)
37+
* Log collector crashes when Redis Enterprise cluster is not running (RED-79996)
38+
* Failures during node showdown and drain process were not preventing node shutdown. Fixed process to do retries. The duration of the retries is controllable via the `redisEnterpriseTerminationGracePeriodSeconds` parameter for the REC (RED-75388)
39+
40+
## API changes
41+
42+
The Redis Enterprise cluster `podSecurityPolicy` is deprecated. This is still supported but will be removed when all K8s versions supporting the feature are removed.
43+
44+
## Compatibility notes
45+
46+
Below is a table showing supported distributions at the time of this release. See [Supported Kubernetes distributions]({{< relref "/kubernetes/reference/supported_k8s_distributions.md" >}}) for the current list of supported distributions.
47+
48+
| **Kubernetes version** | 1.20 | 1.21 | 1.22 | 1.23 | 1.24 |
49+
|:------------------------|:----------:|:----------:|:----------:|:----------:|:----------:|
50+
| Community Kubernetes | | | supported | supported | supported |
51+
| Amazon EKS | | deprecated | supported | supported* |
52+
| Azure AKS | | | supported | supported | supported* |
53+
| Google GKE | | deprecated | supported | supported | supported* |
54+
| Rancher 2.6 | | supported | supported | supported* | |
55+
| **OpenShift version** | **4.7** | **4.8** | **4.9** | **4.10** | **4.11** |
56+
| | deprecated | deprecated | supported | supported | supported* |
57+
| **VMware TKGI version** | **1.11** | **1.12** | **1.13** | **1.14** | **1.15** |
58+
| | deprecated | deprecated | supported* | supported* | |
59+
60+
\* Support added in this release
61+
62+
### Support added
63+
64+
* Azure AKS 1.24
65+
* Amazon EKS 1.23
66+
* Google GKE 1.24
67+
* OpenShift 4.11
68+
* Rancher 1.23
69+
* VMware TKGI 1.14
70+
71+
### Deprecated
72+
73+
* Amazon EKS 1.21
74+
* Google GKE 1.21
75+
* OpenShift 4.7
76+
* OpenShift 4.8
77+
* VMware TKGI 1.11
78+
* VMware TKGI 1.12
79+
80+
### No longer supported
81+
82+
* Community Kubernetes 1.21
83+
* Amazon EKS 1.19, 1.20
84+
* Azure AKS 1.21
85+
* Google GKE 1.19, 1.20
86+
* Rancher 2.6 1.19, 1.20
87+
* VMware TKGI 1.10
88+
89+
## Known limitations
90+
91+
* Long cluster names cause routes to be rejected (RED-25871)
92+
93+
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.
94+
95+
* Cluster CR (REC) errors are not reported after invalid updates (RED-25542)
96+
97+
A cluster CR specification error is not reported if two or more invalid CR resources are updated in sequence.
98+
99+
* An unreachable cluster has status running (RED-32805)
100+
101+
When a cluster is in an unreachable state, the state is still `running` instead of being reported as an error.
102+
103+
* Readiness probe incorrect on failures (RED-39300)
104+
105+
STS Readiness probe does not mark a node as "not ready" when running `rladmin status` on node failure.
106+
107+
* Role missing on replica sets (RED-39002)
108+
109+
The `redis-enterprise-operator` role is missing permission on replica sets.
110+
111+
* Private registries are not supported on OpenShift 3.11 (RED-38579)
112+
113+
OpenShift 3.11 does not support DockerHub private registries. This is a known OpenShift issue.
114+
115+
* Internal DNS and Kubernetes DNS may have conflicts (RED-37462)
116+
117+
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.
118+
119+
* 5.4.10 negatively impacts 5.4.6 (RED-37233)
120+
121+
Kubernetes-based 5.4.10 deployments seem to negatively impact existing 5.4.6 deployments that share a Kubernetes cluster.
122+
123+
* Node CPU usage is reported instead of pod CPU usage (RED-36884)
124+
125+
In Kubernetes, the node CPU usage we report on is the usage of the Kubernetes worker node hosting the REC pod.
126+
127+
* Clusters must be named "rec" in OLM-based deployments (RED-39825)
128+
129+
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".
130+
131+
* REC clusters fail to start on Kubernetes clusters with unsynchronized clocks (RED-47254)
132+
133+
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.
134+
135+
* Deleting an OpenShift project with an REC deployed may hang (RED-47192)
136+
137+
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.
138+
139+
* REC extraLabels are not applied to PVCs on K8s versions 1.15 or older (RED-51921)
140+
141+
In K8s 1.15 or older, the PVC labels come from the match selectors and not the PVC templates. As such, these versions cannot support PVC labels. If this feature is required, the only fix is to upgrade the K8s cluster to a newer version.
142+
143+
* Hashicorp Vault integration - no support for Gesher (RED-55080)
144+
145+
There is no workaround at this time.
146+
147+
* REC might report error states on initial startup (RED-61707)
148+
149+
There is no workaround at this time except to ignore the errors.
150+
151+
* PVC size issues when using decimal value in spec (RED-62132)
152+
153+
The workaround for this issue is to make sure you use integer values for the PVC size.
154+
155+
* Following old revision of quick start guide causes issues creating an REDB due to unrecognized memory field name (RED-69515)
156+
157+
The workaround is to use the newer (current) revision of the quick start document available online.
158+
159+
* `autoUpgrade` set to true by operator might cause unexpected bdb upgrades when `redisUpgradePolicy` is set to true (RED-72351)
160+
161+
Contact support if your deployment is impacted.
162+
163+
* Procedure to update credentials might be problematic on OpenShift when accessing the cluster externally using routes (RS issue)(RED-73251)(RED-75329)
164+
To workaround this, access the API from within the K8s cluster.
165+
166+
* On Windows, `log_collector` doesn't recognize the namespace given with the `-n` flag (RED-83532)
167+
168+
To workaround this, use a different operating system.
169+
170+
* Active-Active database creation will fail if the ingress class annotation is not exactly "nginx" when using Nginx ingress controller (RED-83070)

0 commit comments

Comments
 (0)