K8s: upgrade article fixes (#1182)

kaitlynmichael · zcahana · web-flow · commit 946681be8692 · 2025-02-24T15:55:09.000-06:00
* doc-4859 * copy edits * fix upgrade sections * Update content/operate/kubernetes/release-notes/7-8-4-releases/7-8-4-8-feb25.md Co-authored-by: Zvi Cahana <zcahana@users.noreply.github.com> --------- Co-authored-by: Zvi Cahana <zcahana@users.noreply.github.com>
diff --git a/content/operate/kubernetes/release-notes/7-8-4-releases/7-8-4-8-feb25.md b/content/operate/kubernetes/release-notes/7-8-4-releases/7-8-4-8-feb25.md
@@ -60,5 +60,5 @@ Any distribution not listed below is not supported for production workloads.
 
 - **Redis Enterprise**: `redislabs/redis:7.8.4-66`
 - **Operator**: `redislabs/operator:7.8.4-8`
-- **Services Rigger**: `redislabs/k8s-controller:7.8.`
+- **Services Rigger**: `redislabs/k8s-controller:7.8.4-8`
 - **OLM operator bundle** : `v7.8.4-8.0`
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 7.8.2-6
+Title: Upgrade Redis Enterprise for Kubernetes
 alwaysopen: false
 categories:
 - docs
@@ -27,11 +27,11 @@ For all other Kubernetes distributions, see [Upgrade Redis Enterprise for Kubern
 
 When upgrading, both your Kubernetes version and Redis operator version need to be supported at all times.
 
-{{<warning>}}If your current Kubernetes distribution is not [supported by 7.8.2-6]({{<relref "/operate/kubernetes/release-notes/7-8-2-releases/7-8-2-6-nov24#supported-distributions">}}), upgrade to a supported distribution before upgrading. {{</warning>}}
+{{<warning>}}If your current Kubernetes distribution is not [supported]({{<relref "/operate/kubernetes/reference/supported_k8s_distributions.md">}}), upgrade to a supported distribution before upgrading. {{</warning>}}
 
 ## RHEL9-based image
 
-Redis Enterprise images are now based on Red Hat Enterprise Linux 9 (RHEL9). This means upgrades to 7.8.2-6 require:
+Redis Enterprise images are now based on Red Hat Enterprise Linux 9 (RHEL9). This means upgrades require:
 
 - [Cluster version of 7.4.2-2 or later](https://redis.io/docs/latest/operate/kubernetes/7.4.6/upgrade/).
 - Database version 7.2 or later.
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 7.8.2-6 with OpenShift CLI 
+Title: Upgrade Redis Enterprise with OpenShift CLI 
 alwaysopen: false
 categories:
 - docs
@@ -14,30 +14,30 @@ weight: 20
 Redis implements rolling updates for software upgrades in Kubernetes deployments. The upgrade process includes updating three components:
 
   1. [Upgrade the Redis Enterprise operator](#upgrade-the-operator)
-  1. [Upgrade the Redis Enterprise cluster (REC)](#upgrade-the-redis-enterprise-cluster-rec)
+  1. [Upgrade the Redis Enterprise cluster (REC)](#upgrade-the-redis-enterprise-cluster)
   1. [Upgrade Redis Enterprise databases (REDB)](#upgrade-databases)
 
 ## Prerequisites
 
-The following steps ensure you have the minimum versions of all components necessary to upgrade to 7.8.2-6. **Without these minimum versions, the upgrade will freeze and require manual recovery.**
+The following steps ensure you have the minimum versions of all components necessary to upgrade to 7.8.2-6 or later. **Without these minimum versions, the upgrade will freeze and require manual recovery.**
 
 See the [troubleshooting](#troubleshooting) section for details on recovering a failed upgrade.
 
-### Kubernetes version
+#### Kubernetes version
 
-Check [Supported Kubernetes distributions]({{<relref "/operate/kubernetes/reference/supported_k8s_distributions" >}}) to make sure your Kubernetes distribution is supported by 7.8.2-6. If not, upgrade your Kubernetes distribution before upgrading the Redis operator.
+Check [Supported Kubernetes distributions]({{<relref "/operate/kubernetes/reference/supported_k8s_distributions" >}}) to make sure your Kubernetes distribution is supported. If not, upgrade your Kubernetes distribution before upgrading the Redis operator.
 
-### Redis operator version
+#### Redis operator version
 
-Your Redis Enterprise clusters must be running version 7.4.2-2 or later before upgrading to 7.8.2-6. See the [7.4 upgrade](https://redis.io/docs/latest/operate/kubernetes/7.4.6/upgrade/openshift-cli/) for detailed steps.
+Your Redis Enterprise clusters must be running version 7.4.2-2 or later before upgrading to 7.8.2-6 or later. See the [7.4 upgrade](https://redis.io/docs/latest/operate/kubernetes/7.4.6/upgrade/openshift-cli/) for detailed steps.
 
-### Redis database version
+#### Redis database version
 
-Your Redis databases must be running version 7.2 or later before upgrading your cluster version to 7.8.2-6. 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" >}}).
+Your Redis databases must be running version 7.2 or later before upgrading your cluster version. 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
+#### RHEL9-compatible modules
 
-Upgrading to Redis operator version 7.8.2-6 involves migrating your Redis Enterprise nodes to RHEL9 from either Ubuntu 18 or RHEL8. If your databases use modules, you need to manually install modules compatible with RHEL9.
+Upgrading to Redis operator versions 7.8.2-6 and later  involves migrating your Redis Enterprise nodes to RHEL9 from either Ubuntu 18 or RHEL8. If your databases use modules, you need to manually install modules compatible with RHEL9.
 
 To see which modules you have installed, run:
 
@@ -53,7 +53,7 @@ curl -k -u <rec_username>:<rec_password> -X GET https://localhost:9443/v1/bdbs |
 
 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
+#### Valid license
 
 Use `kubectl get rec` and verify the `LICENSE STATE` is valid on your REC before you start the upgrade process.
 
@@ -143,8 +143,7 @@ oc adm policy add-scc-to-user redis-enterprise-scc-v2 \
 
 If you are upgrading from operator version 6.4.2-6 or before, see the ["after upgrading"](#after-upgrading) section to delete the old SCC and role binding after all clusters are running 6.4.2-6 or later.
 
-## Upgrade the RedisEnterpriseCluster (REC)
-
+## Upgrade the Redis Enterprise Cluster 
 
 {{<warning>}}
 Verify your license is valid before upgrading. Invalid licenses will cause the upgrade to fail.
@@ -154,11 +153,11 @@ Use `oc get rec` and verify the `LICENSE STATE` is valid on your REC before you
 
 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 K8s operator [release notes]({{<relref "/operate/kubernetes/release-notes">}}) to find the Redis Enterprise image tag.
 
 After the operator upgrade is complete, you can upgrade Redis Enterprise cluster (REC).
 
-### Edit `redisEnterpriseImageSpec` in the REC spec
+### Edit `redisEnterpriseImageSpec`
 
 1. Edit the REC custom resource YAML file.
 
@@ -204,7 +203,7 @@ oc rollout status sts <REC_name>
 
 ### Upgrade databases
 
-After the cluster is upgraded, you can upgrade your databases. Specify your new database version in the `spec.redisVersion` field for your REDB and REAADB custom resources. Supported database versions for operator version 7.8.2-6 include `"7.2"` and `"7.4"` (note this value is a string).
+After the cluster is upgraded, you can upgrade your databases. Specify your new database version in the `spec.redisVersion` field for your REDB and REAADB custom resources. Supported database versions include `"7.2"` and `"7.4"` (note this value is a string).
 
 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.
 
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 7.8.2-6 with OpenShift OperatorHub
+Title: Upgrade Redis Enterprise with OpenShift OperatorHub
 alwaysopen: false
 categories:
 - docs
@@ -13,31 +13,31 @@ weight: 40
 
 Redis implements rolling updates for software upgrades in Kubernetes deployments. The upgrade process includes updating three components:
 
-  1. [Upgrade the Redis Enterprise operator](#upgrade-the-operator)
-  1. [Upgrade the Redis Enterprise cluster (REC)](#upgrade-the-redis-enterprise-cluster-rec)
+  1. [Upgrade the Redis Enterprise operator](#upgrade-the-redis-enterprise-operator)
+  1. [Upgrade the Redis Enterprise cluster (REC)](#upgrade-the-redis-enterprise-cluster)
   1. [Upgrade Redis Enterprise databases (REDB)](#upgrade-databases)
 
 ## Prerequisites
 
-The following steps ensure you have the minimum versions of all components necessary to upgrade to 7.8.2-6. **Without these minimum versions, the upgrade will freeze and require manual recovery.**
+The following steps ensure you have the minimum versions of all components necessary to upgrade. **Without these minimum versions, the upgrade will freeze and require manual recovery.**
 
 See the [troubleshooting](#troubleshooting) section for details on recovering a failed upgrade.
 
-### Kubernetes version
+#### Kubernetes version
 
-Check [Supported Kubernetes distributions]({{<relref "/operate/kubernetes/reference/supported_k8s_distributions" >}}) to make sure your Kubernetes distribution is supported by 7.8.2-6. If not, upgrade your Kubernetes distribution before upgrading the Redis operator.
+Check [Supported Kubernetes distributions]({{<relref "/operate/kubernetes/reference/supported_k8s_distributions" >}}) to make sure your Kubernetes distribution is supported. If not, upgrade your Kubernetes distribution before upgrading the Redis operator.
 
-### Redis operator version
+#### Redis operator version
 
 Your Redis Enterprise clusters must be running version 7.4.2-2 or later before upgrading to 7.8.2-6. See the [7.4 upgrade](https://redis.io/docs/latest/operate/kubernetes/7.4.6/upgrade/upgrade-olm/) for detailed steps.
 
-### Redis database version
+#### Redis database version
 
 Your Redis databases must be running version 7.2 or later before upgrading your cluster version to 7.8.2-6. 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
+#### RHEL9-compatible modules
 
-Upgrading to Redis operator version 7.8.2-6 involves 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.
+Upgrading to Redis operator version 7.8.2-6 or later involves migrating your Redis Enterprise nodes to RHEL9 from either Ubuntu 18 or RHEL8. If your databases use modules, you need to manually install modules compatible with RHEL9.
 
 To see which modules you have installed, run:
 
@@ -65,17 +65,18 @@ Use `kubectl get rec` and verify the `LICENSE STATE` is valid on your REC before
 
 3. Verify your **Update approval** is set to "Manual".
 
-4. If you wish to upgrade to the most recent version, set your **Update channel** to "production". If you wish to upgrade to an older version, select it for your Update channel.
+4. To upgrade to the latest version, set your **Update Channel** to ‘production’. To upgrade to an older version, specify the desired version for your **Update Channel**.
 
 5. Select **Upgrade available** shown under **Upgrade status**.
 
 6. When the "Review manual InstallPlan" section appears, select **Preview installPlan** and then **Approve** after reviewing the details. This will start the operator upgrade.
 
-You can monitor the upgrade from the **Installed Operators** page. A new Redis Enterprise Operator will appear in the list, with the status "Installing". The OpenShift will delete the old operator, showing the "Cannot update" status during deletion.
+You can monitor the upgrade from the **Installed Operators** page. A new Redis Enterprise Operator will appear in the list, with the status "Installing". OpenShift will delete the old operator, showing the "Cannot update" status during deletion.
 
 ## Reapply the SCC
 
-If you are using OpenShift, you will also need to manually reapply the [security context constraints](https://docs.openshift.com/container-platform/4.8/authentication/managing-security-context-constraints.html) file ([`scc.yaml`]({{< relref "/operate/kubernetes/deployment/openshift/openshift-cli#deploy-the-operator" >}})) and bind it to your service account.
+
+If you are using OpenShift, you must manually reappply the [security context constraints (SCC)](https://docs.openshift.com/container-platform/4.8/authentication/managing-security-context-constraints.html) file ([`scc.yaml`]({{< relref "/operate/kubernetes/deployment/openshift/openshift-cli#deploy-the-operator" >}})) and bind it to your service account.
 
 ```sh
 oc apply -f openshift/scc.yaml
@@ -85,12 +86,70 @@ oc apply -f openshift/scc.yaml
 oc adm policy add-scc-to-user redis-enterprise-scc-v2 \
   system:serviceaccount:<my-project>:<rec-name>
 ```
+## Upgrade the Redis Enterprise Cluster 
+
+{{<warning>}}
+Verify your license is valid before upgrading. Invalid licenses will cause the upgrade to fail.
+
+Use `oc 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]({{<relref "/operate/kubernetes/release-notes">}}) to find the Redis Enterprise image tag.
+
+After the operator upgrade is complete, you can upgrade Redis Enterprise cluster (REC).
+
+### Edit `redisEnterpriseImageSpec`
+
+1. Edit the REC custom resource YAML file.
+
+    ```sh
+    oc edit rec <your-rec.yaml>
+    ```
+
+1. Replace the `versionTag:` declaration under `redisEnterpriseImageSpec` with the new version tag.
+
+    ```YAML
+    spec:
+      redisEnterpriseImageSpec:
+        imagePullPolicy:  IfNotPresent
+        repository:       redislabs/redis
+        versionTag:       <new-version-tag>
+    ```
+
+1. Save the changes to apply.
+
+### Reapply roles and role bindings
+
+If your operator is monitoring multiple namespaces, you'll need to [reapply your role and role bindings]({{< relref "/operate/kubernetes/re-clusters/multi-namespace#create-role-and-role-binding-for-managed-namespaces" >}}) for each managed namespace. See [Manage databases in multiple namespaces]({{< relref "/operate/kubernetes/re-clusters/multi-namespace" >}}) for more details.
+
+### Monitor the upgrade
+
+You can view the state of the REC with `oc get rec`.
+
+  During the upgrade, the state should be `Upgrade`.
+  When the upgrade is complete and the cluster is ready to use, the state will change to `Running`.
+  If the state is `InvalidUpgrade`, there is an error (usually relating to configuration) in the upgrade.
+
+```sh
+$ oc get rec
+NAME   NODES   VERSION      STATE     SPEC STATUS   LICENSE STATE   SHARDS LIMIT   LICENSE EXPIRATION DATE   AGE
+rec    3       6.2.10-107   Upgrade   Valid         Valid           4              2022-07-16T13:59:00Z      92m
+```
+
+To see the status of the current rolling upgrade, run:
+
+```sh
+oc rollout status sts <REC_name>
+```
 
-### Upgrade databases
+## Upgrade databases
 
-After the cluster is upgraded, you can upgrade your databases. Specify your new database version in the `spec.redisVersion` field for your REDB and REAADB custom resources. Supported database versions for operator version 7.8.2-6 include `"7.2"` and `"7.4"` (note this value is a string).
+After the cluster is upgraded, you can upgrade your databases. Specify your new database version in the `spec.redisVersion` field for your REDB and REAADB custom resources. Supported database versions for this operator version include `"7.2"` and `"7.4"` (note this value is a string).
 
 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.
+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.
 
 ## Troubleshooting
 
