7.8 upgrade prereq

kaitlynmichael · kaitlynmichael · commit 050b5e486f44 · 2024-11-13T15:07:44.000-08:00
diff --git a/content/operate/kubernetes/release-notes/7-8-2-releases/7-8-2-8-nov24.md b/content/operate/kubernetes/release-notes/7-8-2-releases/7-8-2-8-nov24.md
@@ -67,7 +67,7 @@ See [Upgrade Redis Enterprise for Kubernetes]({{<relref "/operate/kubernetes/upg
 - REDB field `upgradeSpec.upgradeModulesToLatest is deprecated.
 - REDB field `spec.modulesList.version` is deprecated.
 
-### Supported distributions
+## 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" >}}).
 
diff --git a/content/operate/kubernetes/upgrade/_index.md b/content/operate/kubernetes/upgrade/_index.md
@@ -1,5 +1,5 @@
 ---
-Title: Upgrade Redis Enterprise for Kubernetes
+Title: Upgrade Redis Enterprise for Kubernetes 7.8.2-2
 alwaysopen: false
 categories:
 - docs
@@ -11,30 +11,32 @@ linkTitle: Upgrade
 weight: 15
 ---
 
-Redis implements rolling updates for software upgrades in Kubernetes deployments. The upgrade process includes updating three components:
+The upgrade process includes updating three components:
 
   1. Upgrade the Redis Enterprise operator
   2. Upgrade the Redis Enterprise cluster (REC)
   3. Upgrade Redis Enterprise databases (REDB)
 
-To use OpenShift container platform CLI to upgrade your Redis Enterprise, see [Upgrade Redis Enterprise with OpenShift CLI]({{< relref "/operate/kubernetes/upgrade/openshift-cli.md" >}}).
+If you are using OpenShift, see [Upgrade Redis Enterprise with OpenShift CLI]({{<relref "/operate/kubernetes/upgrade/openshift-cli">}}) or [Upgrade Redis Enterprise with OpenShift OperatorHub]({{<relref "/operate/kubernetes/upgrade/upgrade-olm">}}).
 
-For all other Kubernetes distributions, see [Upgrade Redis Enterprise for Kubernetes]({{< relref "/operate/kubernetes/upgrade/upgrade-redis-cluster.md" >}}).
+For all other Kubernetes distributions, see [Upgrade Redis Enterprise for Kubernetes]({{<relref "/operate/kubernetes/upgrade/upgrade-redis-cluster" >}}).
 
 ## Upgrade compatibility
 
-When upgrading, both your Kubernetes version and Redis operator version need to be supported at all times. When upgrading your Kubernetes version, you need to make sure both the current and target K8s version are supported by your Redis operator version. When upgrading your Redis operator version, you need make sure both the current and target operator versions are supported by your K8s version. This means if you are planning a large jump in versions, the upgrade might need to be done in multiple steps.
+When upgrading, both your Kubernetes version and Redis operator version need to be supported at all times.
 
-The flow chart below can help you decide if your upgrade requires multiple steps.
+{{<warning>}}If your current Kubernetes distribution is not [supported by 7.8.2-2]({{<relref "/operate/kubernetes/release-notes/7-8-2-releases/7-8-2-8-nov24#supported-distributions">}}), upgrade to a supported distribution before upgrading. {{</warning>}}
 
-{{< image filename="/images/k8s/upgrade-flowchart.jpg" alt="Upgrade flowchart" >}}
+## RHEL9-based image
 
-## How does the REC upgrade work?
+Redis Enterprise images are now based on Red Hat Enterprise Linux 9 (RHEL9). This means upgrades to 7.8.2-2 require:
 
-The Redis Enterprise cluster (REC) uses a rolling upgrade, meaning it upgrades pods one by one. Each pod is updated after the last one completes successfully. This helps keep your cluster available for use.
+- Cluster version of 7.4.2-2 or later.
+- Database version 7.2 or later.
+- RHEL9 compatible binaries for any modules you need.
 
-To upgrade, the cluster terminates each pod and deploys a new pod based on the new image.
-  Before each pod goes down, the operator checks if the pod is a primary (master) for the cluster, and if it hosts any primary (master) shards. If so, a replica on a different pod is promoted to primary. Then when the pod is terminated, the API remains available through the newly promoted primary pod.
+For detailed steps, see the relevant upgrade page:
 
-After a pod is updated, the next pod is terminated and updated.
-After all of the pods are updated, the upgrade process is complete.
+- [OpenShift CLI]({{<relref "/operate/kubernetes/upgrade/openshift-cli">}})
+- [OpenShift OperatorHub]({{<relref "/operate/kubernetes/upgrade/upgrade-olm">}})
+- [Kubernetes]({{<relref "/operate/kubernetes/upgrade/upgrade-redis-cluster" >}})
diff --git a/content/operate/kubernetes/upgrade/openshift-cli.md b/content/operate/kubernetes/upgrade/openshift-cli.md
@@ -1,5 +1,5 @@
 ---
-Title: Upgrade Redis Enterprise with OpenShift CLI
+Title: Upgrade Redis Enterprise 7.8.2-2 with OpenShift CLI 
 alwaysopen: false
 categories:
 - docs
diff --git a/content/operate/kubernetes/upgrade/upgrade-olm.md b/content/operate/kubernetes/upgrade/upgrade-olm.md
@@ -1,5 +1,5 @@
 ---
-Title: Upgrade Redis Enterprise with OpenShift OperatorHub
+Title: Upgrade Redis Enterprise 7.8.2-2 with OpenShift OperatorHub
 alwaysopen: false
 categories:
 - docs
diff --git a/content/operate/kubernetes/upgrade/upgrade-redis-cluster.md b/content/operate/kubernetes/upgrade/upgrade-redis-cluster.md
@@ -1,5 +1,5 @@
 ---
-Title: Upgrade Redis Enterprise for Kubernetes
+Title: Upgrade Redis Enterprise for Kubernetes 7.8.2-2
 alwaysopen: false
 categories:
 - docs
@@ -19,13 +19,43 @@ Redis implements rolling updates for software upgrades in Kubernetes deployments
 
 ## Prerequisites
 
-1. Check [Supported Kubernetes distributions]({{< relref "/operate/kubernetes/reference/supported_k8s_distributions" >}}) to make sure your Kubernetes distribution is supported.
+The following steps ensure you have the minimum versions of all components necessary to upgrade to 7.8.2-2. **Without these minimum versions, a validation error will block the upgrade and it will require manual recovery.**
 
-1. Use `kubectl get rec` and verify the `LICENSE STATE` is valid on your REC before you start the upgrade process.
+See the [troubleshooting](#troubleshooting) section for details on recovering a failed upgrade.
 
-1. Verify you are upgrading from Redis Enterprise operator version 6.2.10-45 or later. If you are not, you must upgrade to 6.2.10-45 before upgrading to versions 6.2.18 or later.
+### Kubernetes version
 
-{{<warning>}}**Upgrade cluster 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]({{< relref "/operate/rs/installing-upgrading/upgrading/upgrade-os" >}})in the Redis Enterprise Software documentation for more details.{{</warning>}}
+Check [Supported Kubernetes distributions]({{<relref "/operate/kubernetes/reference/supported_k8s_distributions" >}}) to make sure your Kubernetes distribution is supported by 7.8.2-2. If not, upgrade your Kubernetes distribution before upgrading the Redis operator.
+
+### Redis operator version
+
+Your Redis Enterprise clusters must be running version 7.4.2-2 or later before upgrading to 7.8.2-2. See the [7.4 upgrade]({{<relref "/operate/kubernetes/7.4.6/upgrade">}}) for detailed steps.
+
+### Redis database version
+
+Your Redis databases must be running version 7.2 or later before upgrading your cluster version to 7.8.2-2. See [upgrade databases](#upgrade-databases) for detailed steps. You can find your database version in the [REDB `spec.redisVersion` field]({{<relref "/operate/kubernetes/reference/redis_enterprise_database_api#redisversion" >}}).
+
+### RHEL9-compatible modules
+
+Upgrading to Redis operator version 7.8.2-2 requires migrating your Redis Enterprise nodes to RHEL9 from either Ubuntu 18 or RHEL8. If your databases use modules, you need to manually install modules compatibile with RHEL9.
+
+To see which modules you have installed, run:
+
+```sh
+curl -k -u <rec_username>:<rec_password> -X GET https://localhost:9443/v1/modules | jq -r 'map([.module_name, .semantic_version, (.platforms | keys)]) | .[] | .[0] as $name | .[1] as $version | .[2][] | $name + "-" + $version + "-" + .' | sort
+```
+
+To see which modules are currently in use, run:
+
+```sh
+curl -k -u <rec_username>:<rec_password> -X GET https://localhost:9443/v1/bdbs | jq -r '.[].module_list | map(.module_name + "-" + .semantic_version) | .[]'
+```
+
+See [Upgrade modules]({{<relref "/operate/oss_and_stack/stack-with-enterprise/install/upgrade-module">}}) for details on how to upgrade modules with the `rladmin` tool.
+
+### Valid license
+
+Use `kubectl get rec` and verify the `LICENSE STATE` is valid on your REC before you start the upgrade process.
 
 ## Upgrade the operator
 
@@ -101,15 +131,9 @@ We recommend upgrading the REC as soon as possible after updating the operator.
 
 ## Upgrade the Redis Enterprise cluster (REC)
 
-{{<warning>}}
-Verify your license is valid before upgrading. Invalid licenses will cause the upgrade to fail.
-
-Use `kubectl get rec` and verify the `LICENSE STATE` is valid on your REC before you start the upgrade process.
-{{</warning>}}
-
 The Redis Enterprise cluster (REC) can be updated automatically or manually. To trigger automatic upgrade of the REC after the operator upgrade completes, specify `autoUpgradeRedisEnterprise: true` in your REC spec. If you don't have automatic upgrade enabled, follow the below steps for the manual upgrade.
 
-Before beginning the upgrade of the Redis Enterprise cluster, check the K8s operator release notes to find the Redis Enterprise image tag. For example, in Redis Enterprise K8s operator release [6.0.12-5](https://github.com/RedisLabs/redis-enterprise-k8s-docs/releases/tag/v6.0.12-5), the `Images` section shows the Redis Enterprise tag is `6.0.12-57`.
+Before beginning the upgrade of the Redis Enterprise cluster, check the [Redis Enterprise for Kubernetes release notes]({{<relref "/operate/kubernetes/release-notes/7-8-2-releases">}}) to find the Redis Enterprise image tag.
 
 After the operator upgrade is complete, you can upgrade Redis Enterprise cluster (REC).
 
@@ -167,8 +191,10 @@ kubectl rollout status sts <REC_name>
 
 After the cluster is upgraded, you can upgrade your databases. The process for upgrading databases is the same for both Kubernetes and non-Kubernetes deployments.
 
-For more details on how to [upgrade a database]({{< relref "/operate/rs/installing-upgrading/upgrading/upgrade-database" >}}), see the [Upgrade an existing Redis Enterprise Software deployment]({{< relref "/operate/rs/installing-upgrading/upgrading" >}}) documentation.
+For more details on how to [upgrade a database]({{<relref "/operate/rs/installing-upgrading/upgrading/upgrade-database" >}}), see the [Upgrade an existing Redis Enterprise Software deployment]({{<relref "/operate/rs/installing-upgrading/upgrading" >}}) documentation.
 
 For Active-Active databases, see [Upgrade an Active-Active database]({{<relref "/operate/rs/installing-upgrading/upgrading/upgrade-active-active">}}).
 
-Note that if your cluster [`redisUpgradePolicy`]({{< relref "/operate/kubernetes/reference/redis_enterprise_cluster_api#redisupgradepolicy" >}}) or your database [`redisVersion`]({{< relref "/operate/kubernetes/reference/redis_enterprise_database_api#redisversion" >}}) are set to `major`, you won't be able to upgrade those databases to minor versions. See [Redis upgrade policy]({{< relref "/operate/rs/installing-upgrading/upgrading#redis-upgrade-policy" >}}) for more details.
+Note that if your cluster [`redisUpgradePolicy`]({{<relref "/operate/kubernetes/reference/redis_enterprise_cluster_api#redisupgradepolicy" >}}) or your database [`redisVersion`]({{< relref "/operate/kubernetes/reference/redis_enterprise_database_api#redisversion" >}}) are set to `major`, you won't be able to upgrade those databases to minor versions. See [Redis upgrade policy]({{< relref "/operate/rs/installing-upgrading/upgrading#redis-upgrade-policy" >}}) for more details.
+
+## Troubleshooting
