add release details

Author: kaitlynmichael

content/operate/kubernetes/release-notes/8-0-2-releases/8-0-2-2-october2025.md

@@ -11,52 +11,88 @@ title: Redis Enterprise for Kubernetes 8.0.2-2 (October 2025) release notes
 weight: 1
 ---
 
+This feature release of Redis Enterprise for Kubernetes supports Redis Software 8.0.2-17 and includes enhancements, platform support changes, and bug fixes.
 
-## New in the release
-### Enhancements
+{{< warning >}}
+**Custom modules not supported**: If you use custom (non-bundled) modules, skip this release. Custom module support will be available in the next release.
+{{< /warning >}}
+
+## New in this release
+
+This release includes enhancements to the Redis Enterprise for Kubernetes operator, and includes features supported by Redis Software 8.0.2-17, and Redis Open Source 8.0 and 8.2.
+
+**Redis Enterprise for Kubernetes 8.0.2-2:**
+This release includes enhancements to Redis Enterprise for Kubernetes including:
 
 - Support for RS 8.0.2-17
 - Support for the VKS platform (Broadcom/VMWare)
 - Added container probes to Redis Enterprise pods
 - Kubernetes 1.34 support (select platforms)
 - Unique per release CSV/OperatorHub channels
 
+**Redis Software 8.0.2-17:**
+
+- Automatically enabled capabilities (modules) in Redis 8
+- Metrics stream engine
+- Module management enhancements
+- Lag-aware availability API
+- Redis Flex (Redis on Flash version 2)
+
+For more information about Redis Software 8.0.2-17, see the [Redis Software 8.0.2-17 release notes]({{< relref "/operate/rs/release-notes/rs-8-0-2-releases/rs-8-0-2-17.md" >}}).
+
+**Redis Open Source 8.0 and 8.2:**
+
+- Preview of new vector set data type
+- Redis query engine improvements
+- Performance improvements
+- Enhanced ACLs
+- New hash and streams commands
+
+For more details, see [What's new in Redis 8.0]({{< relref "/develop/whats-new/8-0/" >}}) and [Redis Open Source 8.2 release notes]({{< relref "/operate/oss_and_stack/stack-with-enterprise/release-notes/redisce/redisos-8.0-release-notes/" >}}).
+
 ### Resolved issues
 
-- Operator logs don't reflect the exact filed inconsistent between REC and STS (RED-161426)
-- Security fixes (RED-162939, RED-163832, RED-165628, RED-168087)
-- BDB tags defined by RS users are overridden (RED-170322)
+- Fixed operator logs to properly reflect field inconsistencies between REC and statefulset (RED-161426)
+- Applied security fixes (RED-162939, RED-163832, RED-165628, RED-168087)
+- Fixed database tags being overridden when defined by Redis Software users (RED-170322)
 
 ### API changes
+
 | **CRD** | **Field** | **Change** | **Description** |
 |---|---|---|---|
-| REAADB | `spec.alertSettings.bdb_proxy_cert_expiring_soon` | Add | Enable a new alert in alert settings |
+| REAADB | `spec.alertSettings.bdb_proxy_cert_expiring_soon` | Add | Enables a new alert in alert settings |
 | REC | | Change | Changed the storage version of the API to v1 (from v1alpha1) |
-| REDB | `spec.alertSettings.bdb_proxy_cert_expiring_soon` | Add | Enable a new alert in alert settings |
-| REDB | `spec.moduleList` | Change | For Redis version 8 and above, bundled modules are enabled automatically, so there is no need to specify them |
-| REDB | `spec.moduleList.[DbModule].version` | Change | Module versions in regular deployments are automatically selected by the Redis Enterprise cluster. Specified module versions will be ignored. In Active-Active setups - module version must be specified. |
+| REDB | `spec.alertSettings.bdb_proxy_cert_expiring_soon` | Add | Enables a new alert in alert settings |
+| REDB | `spec.moduleList` | Change | For Redis version 8 and later, bundled modules are enabled automatically, so you don't need to specify them |
+| REDB | `spec.moduleList.[DbModule].version` | Change | Module versions in regular deployments are automatically selected by the Redis Enterprise cluster. Specified module versions are ignored. In Active-Active setups, you must specify the module version. |
 
 ## Version changes
 
 ### Breaking changes
 
-- Using non bundled modules not supported with this version. Users using such modules are not advised to upgrade to the version. The Redis Enterprise version used with this operator version has gone through significant changes around modules including using built in modules by default on databases. See the redis enterprise core software release notes for further details.
-- TKG (TKGm) is no longer supported. This platform is not planned to be supported by Broadcom/VMWare in the near future and customers are encouraged to move to TKGI/VKS.
+- **Non-bundled modules are not supported** with this version. If you use non-bundled modules, don't upgrade to this version. The Redis Enterprise version used with this operator version includes significant changes to modules, including using built-in modules by default on databases. For more details, see the Redis Enterprise core software release notes.
+
+- **TKG (TKGm) is no longer supported**. Broadcom/VMware doesn't plan to support this platform in the near future. We recommend that you migrate to TKGI/VKS.
+
+For additional breaking changes related to Redis Software 8.0.2-17, see [Redis 8 breaking changes]({{< relref "/operate/rs/release-notes/rs-8-0-releases/rs-8-0-2-17#redis-8-breaking-changes" >}}).
+
+For additional Redis Software breaking changes, see [Redis 8 breaking changes](https://redis.io/docs/staging/release-rs-gilboa/operate/rs/release-notes/rs-8-0-releases/rs-8-0-2-17/#redis-8-breaking-changes).
 
 ### Deprecations
 
-- The usage of the REC v1alpha1 API version is deprecated.
+- The RedisEnterpriseCluster (REC) v1alpha1 API version 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]({{< relref "/operate/kubernetes/reference/supported_k8s_distributions" >}}).
 
-<span title="Check mark icon">&#x2705;</span> Supported – This distribution is supported for this version of Redis Enterprise Software for Kubernetes.
+<span title="Check mark icon">&#x2705;</span> **Supported** – This distribution is supported for this version of Redis Enterprise Software for Kubernetes.
 
-<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.
+<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.
 
-<span title="X icon">&#x274c;</span> End of life – Support for this distribution ended.
+<span title="X icon">&#x274c;</span> **End of life** – Support for this distribution ended.
 
-Any distribution not listed below is not supported for production workloads.
+Any distribution not listed in the table is not supported for production workloads.
 
 | Kubernetes version | **1.28** | **1.29** | **1.30** | **1.31** | **1.32** | **1.33** | **1.34** |
 |---|---|---|---|---|---|---|---|
@@ -76,7 +112,6 @@ Any distribution not listed below is not supported for production workloads.
 |---|---|---|---|---|---|---|---|
 | | <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> | | | |
 
-
 ## Downloads
 
 
@@ -86,5 +121,6 @@ Any distribution not listed below is not supported for production workloads.
 - **Callhome client**: `redislabs/re-call-home-client:8.0.2-2`
 - **OLM operator bundle** : `v.<TBD>`
 
-
 ## Known limitations
+
+See [8.0.2 releases]({{<relref "/operate/kubernetes/release-notes/8-0-2-releases/">}}) for information on known limitations.

content/operate/kubernetes/release-notes/8-0-2-releases/_index.md

@@ -25,3 +25,33 @@ Redis Enterprise for Kubernetes 8.0.2-2 includes bug fixes, enhancements, and su
 
 
 ## Known limitations
+
+- **PVC expansion is not supported when using Redis on Flash (Auto Tiering)** - Do not enable enablePersistentVolumeResize if your REC uses redisOnFlashSpec as this will result in conflicts (RED-165770)
+- **Specifying databasePort causes issues with REAADB synchronization** (RED-149374)
+- **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
+- **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
+- **Missing endpoint for admission endpoint (rare)** - Restart the operator pod (RED-119469)
+- **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** - Wait until the services rigger pod has finished to terminate it (RED-107687)
+- **REAADB changes might fail with "gateway timeout" errors, mostly on OpenShift** - Retry the operation (RED-103048)
+- **Installing operator bundle produces warning: "Warning: would violate PodSecurity "restricted:v1.24""** - Ignore the warning (RED-97381)
+- **RERC resources must have a unique name** - The string rec-name/rec-namespace must be different from all other participating clusters in the Active-Active database (RED-96302)
+- **Admission is not blocking REAADB with shardCount which exceeds license quota** - Fix the problems with the REAADB and reapply (RED-96301)
+- **Active-Active controller only supports global database options. Configuration specific to location is not supported** (RED-86490)
+- **autoUpgrade set to true can cause unexpected bdb upgrades when redisUpgradePolicy is set to true** - Contact support if your deployment is impacted (RED-72351)
+- **Following the previous quick start guide version causes issues with creating an REDB due to unrecognized memory field name** - Use the newer (current) revision of Deploy Redis Enterprise Software for Kubernetes (RED-69515)
+- **PVC size issues when using decimal value in spec** - Make sure you use integer values for the PVC size (RED-62132)
+- **REC might report error states on initial startup** - There is no workaround at this time except to ignore the errors (RED-61707)
+- **Hashicorp Vault integration - no support for Gesher** - There is no workaround for this issue. Gesher support has been deprecated (RED-55080)
+- **REC clusters fail to start on Kubernetes clusters with unsynchronized clocks** - 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 (RED-47254)
+- **Deleting an OpenShift project with an REC deployed may hang** - 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. The fix is to delete the REDB resources first and the REC second (RED-47192)
+- **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 name (i.e., "rec"). Naming the cluster "rec" should resolve the issue (RED-39825)
+- **STS Readiness prob doesn't mark a node as "not ready when" rladmin status nodes fails** (RED-39300)
+- **DNS conflicts are possible between the cluster mdns_server and the K8s DNS** - Only impacts DNS resolution from within cluster nodes (RED-37462)
+- **K8S-based 5.4.10 clusters seem to negatively affect existing 5.4.6 clusters** (RED-37233)
+- **In Kubernetes, the node CPU usage we report is the usage of the K8S worker node hosting the REC pod** (RED-36884)
+- **When a cluster is in an unreachable state, the cluster is still running instead of being reported as an error** (RED-32805)
+- **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** - Limit cluster name to 20 characters or less (RED-25871)
+- **A cluster CR specification error is not reported if two or more invalid CR resources are updated in sequence** (RED-25542)
+- **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** - Avoid duplicating database names. Database creation via K8s has validation in place to prevent this (RED-99997)
+- **Active-Active setup removal might keep services or routes undeleted** - Delete services or routes manually if you encounter this problem (RED-77752)