From fac46a62613fa04fc1d916048693daa171c0bb29 Mon Sep 17 00:00:00 2001 From: Kaitlyn Michael Date: Wed, 19 Feb 2025 14:15:29 -0600 Subject: [PATCH 1/4] doc-4859 --- .../kubernetes/release-notes/7-8-4-releases/7-8-4-8-feb25.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) 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 index 47ebbdf30c..2aabf2f7b4 100644 --- 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.84-8.` - **OLM operator bundle** : `v7.8.4-8.0` \ No newline at end of file From 3daa73141f0004978ebe114870650affdc48d400 Mon Sep 17 00:00:00 2001 From: Kaitlyn Michael Date: Wed, 19 Feb 2025 14:33:15 -0600 Subject: [PATCH 2/4] copy edits --- content/operate/kubernetes/upgrade/_index.md | 6 +- .../kubernetes/upgrade/openshift-cli.md | 14 ++-- .../operate/kubernetes/upgrade/upgrade-olm.md | 73 ++++++++++++++++--- 3 files changed, 74 insertions(+), 19 deletions(-) diff --git a/content/operate/kubernetes/upgrade/_index.md b/content/operate/kubernetes/upgrade/_index.md index 663869ec0b..8dc01c7ecf 100644 --- 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. -{{}}If your current Kubernetes distribution is not [supported by 7.8.2-6]({{}}), upgrade to a supported distribution before upgrading. {{}} +{{}}If your current Kubernetes distribution is not [supported]({{}}), upgrade to a supported distribution before upgrading. {{}} ## 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 index 17a795f678..7e2a19a1e8 100644 --- 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 @@ -19,25 +19,25 @@ Redis implements rolling updates for software upgrades in Kubernetes deployments ## 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 -Check [Supported Kubernetes 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]({{}}) to make sure your Kubernetes distribution is supported. 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-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 -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]({{}}). +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]({{}}). ### 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: @@ -204,7 +204,7 @@ oc rollout status sts ### 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`]({{}}) 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 index 110eaf52f1..80f007660b 100644 --- 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,19 +13,19 @@ 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 operator](#upgrade-the-redis-enterprise-operator) 1. [Upgrade the Redis Enterprise cluster (REC)](#upgrade-the-redis-enterprise-cluster-rec) 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 -Check [Supported Kubernetes 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]({{}}) to make sure your Kubernetes distribution is supported. If not, upgrade your Kubernetes distribution before upgrading the Redis operator. ### Redis operator version @@ -37,7 +37,7 @@ Your Redis databases must be running version 7.2 or later before upgrading your ### 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,17 @@ 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 @@ -88,9 +88,64 @@ oc adm policy add-scc-to-user redis-enterprise-scc-v2 \ ### 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`]({{}}) 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. + +Before beginning the upgrade of the Redis Enterprise cluster, check the [Redis Enterprise for Kubernetes release notes]({{}}) to find the Redis Enterprise image tag. + +After the operator upgrade is complete, you can upgrade Redis Enterprise cluster (REC). + +### Upgrade an REC with an Active-Active database + +We recommend upgrading all participating clusters to the same operator version. + +If you are upgrading from a preview version of the Active-Active controller, you can remove the following environment variables: `ACTIVE_ACTIVE_DATABASE_CONTROLLER_ENABLED`, `REMOTE_CLUSTER_CONTROLLER_ENABLED`, and `ENABLE_ALPHA_FEATURES`. + +### Edit `redisEnterpriseImageSpec` in the REC spec + +1. Edit the REC custom resource YAML file. + + ```sh + kubectl edit rec + ``` + +1. Replace the `versionTag:` declaration under `redisEnterpriseImageSpec` with the new version tag. + + ```YAML + spec: + redisEnterpriseImageSpec: + imagePullPolicy: IfNotPresent + repository: redislabs/redis + versionTag: + ``` + +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 `kubectl 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 +$ kubectl 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 +kubectl rollout status sts +``` ## Troubleshooting From 160fe29b75a441a35bf39caa1ba39c9f9624462c Mon Sep 17 00:00:00 2001 From: Kaitlyn Michael Date: Wed, 19 Feb 2025 14:55:37 -0600 Subject: [PATCH 3/4] fix upgrade sections --- .../kubernetes/upgrade/openshift-cli.md | 19 ++++---- .../operate/kubernetes/upgrade/upgrade-olm.md | 44 ++++++++++--------- 2 files changed, 33 insertions(+), 30 deletions(-) diff --git a/content/operate/kubernetes/upgrade/openshift-cli.md b/content/operate/kubernetes/upgrade/openshift-cli.md index 7e2a19a1e8..dc90753b54 100644 --- a/content/operate/kubernetes/upgrade/openshift-cli.md +++ b/content/operate/kubernetes/upgrade/openshift-cli.md @@ -14,7 +14,7 @@ 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 @@ -23,19 +23,19 @@ The following steps ensure you have the minimum versions of all components neces See the [troubleshooting](#troubleshooting) section for details on recovering a failed upgrade. -### Kubernetes version +#### Kubernetes version Check [Supported Kubernetes 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 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. See [upgrade databases](#upgrade-databases) for detailed steps. You can find your database version in the [REDB `spec.redisVersion` field]({{}}). -### RHEL9-compatible modules +#### RHEL9-compatible modules 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. @@ -53,7 +53,7 @@ curl -k -u : -X GET https://localhost:9443/v1/bdbs | See [Upgrade modules]({{}}) 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 {{}} 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]({{}}) 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. diff --git a/content/operate/kubernetes/upgrade/upgrade-olm.md b/content/operate/kubernetes/upgrade/upgrade-olm.md index 80f007660b..6082ddcd08 100644 --- a/content/operate/kubernetes/upgrade/upgrade-olm.md +++ b/content/operate/kubernetes/upgrade/upgrade-olm.md @@ -14,7 +14,7 @@ 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-redis-enterprise-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 @@ -23,19 +23,19 @@ The following steps ensure you have the minimum versions of all components neces See the [troubleshooting](#troubleshooting) section for details on recovering a failed upgrade. -### Kubernetes version +#### Kubernetes version Check [Supported Kubernetes 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]({{}}). -### RHEL9-compatible modules +#### RHEL9-compatible modules 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. @@ -75,6 +75,7 @@ You can monitor the upgrade from the **Installed Operators** page. A new Redis E ## Reapply the SCC + 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 @@ -85,30 +86,26 @@ oc apply -f openshift/scc.yaml oc adm policy add-scc-to-user redis-enterprise-scc-v2 \ system:serviceaccount:: ``` +## Upgrade the Redis Enterprise Cluster -### Upgrade databases +{{}} +Verify your license is valid before upgrading. Invalid licenses will cause the upgrade to fail. -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). +Use `oc get rec` and verify the `LICENSE STATE` is valid on your REC before you start the upgrade process. +{{}} -Note that if your cluster [`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. -Before beginning the upgrade of the Redis Enterprise cluster, check the [Redis Enterprise for Kubernetes release notes]({{}}) to find the Redis Enterprise image tag. +Before beginning the upgrade of the Redis Enterprise cluster, check the K8s operator [release notes]({{}}) to find the Redis Enterprise image tag. After the operator upgrade is complete, you can upgrade Redis Enterprise cluster (REC). -### Upgrade an REC with an Active-Active database - -We recommend upgrading all participating clusters to the same operator version. - -If you are upgrading from a preview version of the Active-Active controller, you can remove the following environment variables: `ACTIVE_ACTIVE_DATABASE_CONTROLLER_ENABLED`, `REMOTE_CLUSTER_CONTROLLER_ENABLED`, and `ENABLE_ALPHA_FEATURES`. - -### Edit `redisEnterpriseImageSpec` in the REC spec +### Edit `redisEnterpriseImageSpec` 1. Edit the REC custom resource YAML file. ```sh - kubectl edit rec + oc edit rec ``` 1. Replace the `versionTag:` declaration under `redisEnterpriseImageSpec` with the new version tag. @@ -129,14 +126,14 @@ If your operator is monitoring multiple namespaces, you'll need to [reapply your ### Monitor the upgrade -You can view the state of the REC with `kubectl get rec`. +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 -$ kubectl get rec +$ 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 ``` @@ -144,9 +141,16 @@ rec 3 6.2.10-107 Upgrade Valid Valid 4 To see the status of the current rolling upgrade, run: ```sh -kubectl rollout status sts +oc rollout status sts ``` +## 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 this operator version include `"7.2"` and `"7.4"` (note this value is a string). + +Note that if your cluster [`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 If you start an upgrade without meeting the [prerequisites](#prerequisites), the operator will freeze the upgrade. Check the operator logs for the source of the error. The REDB reconsilliation doesn't work during an upgrade, so you need to apply a manual fix with the Redis Software API (examples below). The updates will also need to be added to the REDB custom resource. From da51c95d3be82ea1651f53b3ea85c64c6e4c9511 Mon Sep 17 00:00:00 2001 From: Kaitlyn Michael <76962844+kaitlynmichael@users.noreply.github.com> Date: Thu, 20 Feb 2025 13:37:21 -0600 Subject: [PATCH 4/4] Update content/operate/kubernetes/release-notes/7-8-4-releases/7-8-4-8-feb25.md Co-authored-by: Zvi Cahana --- .../kubernetes/release-notes/7-8-4-releases/7-8-4-8-feb25.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) 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 index 2aabf2f7b4..b38c24b3d4 100644 --- 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.84-8.` +- **Services Rigger**: `redislabs/k8s-controller:7.8.4-8` - **OLM operator bundle** : `v7.8.4-8.0` \ No newline at end of file