From e88dacdfb3095ff0957d810ac4e11eaf2e78d775 Mon Sep 17 00:00:00 2001 From: Kevin A Date: Thu, 3 Aug 2023 09:47:27 -0700 Subject: [PATCH] Update upgrades.md (#747) Although we don't have confirmation that this applies to earlier versions of Rancher (2.6 and below) I'm merging as the information is important for the latest (2.7). Specifically, it's not clear to me from the AWS site if you can install earlier versions. * Update upgrades.md Add consideration for the current 'Rancher Setup' AWS Marketplace offering, which uses the deployment name of 'rancher-setup'. * Apply suggestions from code review * versioned docs sync to 2.7 --------- Co-authored-by: Marty Hernandez Avedon Co-authored-by: martyav --- .../upgrades.md | 23 +++++++++++++++++++ .../upgrades.md | 19 +++++++++++++++ 2 files changed, 42 insertions(+) diff --git a/docs/getting-started/installation-and-upgrade/install-upgrade-on-a-kubernetes-cluster/upgrades.md b/docs/getting-started/installation-and-upgrade/install-upgrade-on-a-kubernetes-cluster/upgrades.md index 6bad4e4ca2a..ffdceed87e4 100644 --- a/docs/getting-started/installation-and-upgrade/install-upgrade-on-a-kubernetes-cluster/upgrades.md +++ b/docs/getting-started/installation-and-upgrade/install-upgrade-on-a-kubernetes-cluster/upgrades.md @@ -131,6 +131,17 @@ There will be more values that are listed with this command. This is just an exa ::: +:::tip + +Your deployment name may vary; for example, if you're deploying Rancher through the AWS Marketplace, the deployment name is 'rancher-stable'. +Thus: +``` +helm get values rancher-stable -n cattle-system + +hostname: rancher.my.org +``` + +::: If you are upgrading cert-manager to the latest version from v1.5 or below, follow the [cert-manager upgrade docs](../resources/upgrade-cert-manager.md#option-c-upgrade-cert-manager-from-versions-15-and-below) to learn how to upgrade cert-manager without needing to perform an uninstall or reinstall of Rancher. Otherwise, follow the [steps to upgrade Rancher](#steps-to-upgrade-rancher) below. @@ -154,6 +165,18 @@ The above is an example, there may be more values from the previous step that ne ::: +:::tip + +If you deploy Rancher through the AWS Marketplace, the deployment name is 'rancher-stable'. +Thus: +``` +helm upgrade rancher-stable rancher-/rancher \ + --namespace cattle-system \ + --set hostname=rancher.my.org +``` + +::: + Alternatively, it's possible to export the current values to a file and reference that file during upgrade. For example, to only change the Rancher version: 1. Export the current values to a file: diff --git a/versioned_docs/version-2.7/getting-started/installation-and-upgrade/install-upgrade-on-a-kubernetes-cluster/upgrades.md b/versioned_docs/version-2.7/getting-started/installation-and-upgrade/install-upgrade-on-a-kubernetes-cluster/upgrades.md index cfd3e62cb71..fb4f1cf42bb 100644 --- a/versioned_docs/version-2.7/getting-started/installation-and-upgrade/install-upgrade-on-a-kubernetes-cluster/upgrades.md +++ b/versioned_docs/version-2.7/getting-started/installation-and-upgrade/install-upgrade-on-a-kubernetes-cluster/upgrades.md @@ -131,6 +131,15 @@ There will be more values that are listed with this command. This is just an exa ::: +:::tip +Your deployment name may vary; for example, if you're deploying Rancher through the AWS Marketplace, the deployment name is 'rancher-stable'. +Thus: +``` +helm get values rancher-stable -n cattle-system + +hostname: rancher.my.org +``` +::: If you are upgrading cert-manager to the latest version from v1.5 or below, follow the [cert-manager upgrade docs](../resources/upgrade-cert-manager.md#option-c-upgrade-cert-manager-from-versions-15-and-below) to learn how to upgrade cert-manager without needing to perform an uninstall or reinstall of Rancher. Otherwise, follow the [steps to upgrade Rancher](#steps-to-upgrade-rancher) below. @@ -154,6 +163,16 @@ The above is an example, there may be more values from the previous step that ne ::: +:::tip +If you deploy Rancher through the AWS Marketplace, the deployment name is 'rancher-stable'. +Thus: +``` +helm upgrade rancher-stable rancher-/rancher \ + --namespace cattle-system \ + --set hostname=rancher.my.org +``` +::: + Alternatively, it's possible to export the current values to a file and reference that file during upgrade. For example, to only change the Rancher version: 1. Export the current values to a file: