upgrade: add v1.1.3 upgrade path

Signed-off-by: Kiefer Chang <[email protected]>
harvester · Jun 13, 2024 · f809222 · f809222
1 parent 8784f5a
commit f809222
Show file tree

Hide file tree

Showing 6 changed files with 12 additions and 12 deletions.
diff --git a/docs/upgrade/automatic.md b/docs/upgrade/automatic.md
@@ -23,7 +23,7 @@ The following table shows the upgrade path of all supported versions.
 | Upgrade from version | Supported new version(s) |
 |----------------------|--------------------------|
 | [v1.2.1](./v1-2-1-to-v1-2-2.md) | v1.2.2        |
-| [v1.1.2/v1.2.0](./v1-2-0-to-v1-2-1.md) | v1.2.1              |
+| [v1.1.2/v1.1.3/v1.2.0](./v1-2-0-to-v1-2-1.md) | v1.2.1              |
 | [v1.1.1/v1.1.2](./v1-1-1-to-v1-1-3.md) | v1.1.3        |
 | [v1.1.0/v1.1.1](./v1-1-to-v1-1-2.md) | v1.1.2        |
 

diff --git a/docs/upgrade/v1-2-0-to-v1-2-1.md b/docs/upgrade/v1-2-0-to-v1-2-1.md
@@ -1,7 +1,7 @@
 ---
 sidebar_position: 3
-sidebar_label: Upgrade from v1.1.2/v1.2.0 to v1.2.1
-title: "Upgrade from v1.1.2/v1.2.0 to v1.2.1"
+sidebar_label: Upgrade from v1.1.2/v1.1.3/v1.2.0 to v1.2.1
+title: "Upgrade from v1.1.2/v1.1.3/v1.2.0 to v1.2.1"
 ---
 
 <head>
@@ -11,7 +11,7 @@ title: "Upgrade from v1.1.2/v1.2.0 to v1.2.1"
 
 ## Important changes to this version
 
-Harvester `v1.2.1` fixes upgrade known issues found in `v1.2.0`, we suggest upgrading `v1.1.2` and `v1.2.0` clusters to `v1.2.1`. The known issues found in `v1.2.0` are:
+Harvester `v1.2.1` fixes upgrade known issues found in `v1.2.0`, we suggest upgrading `v1.1.2`, `v1.1.3`, or `v1.2.0` clusters to `v1.2.1`. The known issues found in `v1.2.0` are:
 - [An Upgrade is stuck in the Post-draining state](./v1-1-2-to-v1-2-0.md#9-an-upgrade-is-stuck-in-the-post-draining-state)
 - [An upgrade is stuck in the Upgrading System Service state due to the customer provided SSL certificate without IP SAN error in fleet-agent](./v1-1-2-to-v1-2-0.md#10-an-upgrade-is-stuck-in-the-upgrading-system-service-state-due-to-the-customer-provided-ssl-certificate-without-ip-san-error-in-fleet-agent)
 

diff --git a/versioned_docs/version-v1.2/upgrade/automatic.md b/versioned_docs/version-v1.2/upgrade/automatic.md
@@ -23,7 +23,7 @@ The following table shows the upgrade path of all supported versions.
 | Upgrade from version | Supported new version(s) |
 |----------------------|--------------------------|
 | [v1.2.1](./v1-2-1-to-v1-2-2.md) | v1.2.2        |
-| [v1.1.2/v1.2.0](./v1-2-0-to-v1-2-1.md) | v1.2.1              |
+| [v1.1.2/v1.1.3/v1.2.0](./v1-2-0-to-v1-2-1.md) | v1.2.1              |
 | [v1.1.1/v1.1.2](./v1-1-1-to-v1-1-3.md) | v1.1.3        |
 | [v1.1.0/v1.1.1](./v1-1-to-v1-1-2.md) | v1.1.2        |
 

diff --git a/versioned_docs/version-v1.2/upgrade/v1-2-0-to-v1-2-1.md b/versioned_docs/version-v1.2/upgrade/v1-2-0-to-v1-2-1.md
@@ -1,7 +1,7 @@
 ---
 sidebar_position: 3
-sidebar_label: Upgrade from v1.1.2/v1.2.0 to v1.2.1
-title: "Upgrade from v1.1.2/v1.2.0 to v1.2.1"
+sidebar_label: Upgrade from v1.1.2/v1.1.3/v1.2.0 to v1.2.1
+title: "Upgrade from v1.1.2/v1.1.3/v1.2.0 to v1.2.1"
 ---
 
 <head>
@@ -11,7 +11,7 @@ title: "Upgrade from v1.1.2/v1.2.0 to v1.2.1"
 
 ## Important changes to this version
 
-Harvester `v1.2.1` fixes upgrade known issues found in `v1.2.0`, we suggest upgrading `v1.1.2` and `v1.2.0` clusters to `v1.2.1`. The known issues found in `v1.2.0` are:
+Harvester `v1.2.1` fixes upgrade known issues found in `v1.2.0`, we suggest upgrading `v1.1.2`, `v1.1.3`, or `v1.2.0` clusters to `v1.2.1`. The known issues found in `v1.2.0` are:
 - [An Upgrade is stuck in the Post-draining state](./v1-1-2-to-v1-2-0.md#9-an-upgrade-is-stuck-in-the-post-draining-state)
 - [An upgrade is stuck in the Upgrading System Service state due to the customer provided SSL certificate without IP SAN error in fleet-agent](./v1-1-2-to-v1-2-0.md#10-an-upgrade-is-stuck-in-the-upgrading-system-service-state-due-to-the-customer-provided-ssl-certificate-without-ip-san-error-in-fleet-agent)
 

diff --git a/versioned_docs/version-v1.3/upgrade/automatic.md b/versioned_docs/version-v1.3/upgrade/automatic.md
@@ -23,7 +23,7 @@ The following table shows the upgrade path of all supported versions.
 | Upgrade from version | Supported new version(s) |
 |----------------------|--------------------------|
 | [v1.2.1](./v1-2-1-to-v1-2-2.md) | v1.2.2        |
-| [v1.1.2/v1.2.0](./v1-2-0-to-v1-2-1.md) | v1.2.1              |
+| [v1.1.2/v1.1.3/v1.2.0](./v1-2-0-to-v1-2-1.md) | v1.2.1              |
 | [v1.1.1/v1.1.2](./v1-1-1-to-v1-1-3.md) | v1.1.3        |
 | [v1.1.0/v1.1.1](./v1-1-to-v1-1-2.md) | v1.1.2        |
 

diff --git a/versioned_docs/version-v1.3/upgrade/v1-2-0-to-v1-2-1.md b/versioned_docs/version-v1.3/upgrade/v1-2-0-to-v1-2-1.md
@@ -1,7 +1,7 @@
 ---
 sidebar_position: 3
-sidebar_label: Upgrade from v1.1.2/v1.2.0 to v1.2.1
-title: "Upgrade from v1.1.2/v1.2.0 to v1.2.1"
+sidebar_label: Upgrade from v1.1.2/v1.1.3/v1.2.0 to v1.2.1
+title: "Upgrade from v1.1.2/v1.1.3/v1.2.0 to v1.2.1"
 ---
 
 <head>
@@ -11,7 +11,7 @@ title: "Upgrade from v1.1.2/v1.2.0 to v1.2.1"
 
 ## Important changes to this version
 
-Harvester `v1.2.1` fixes upgrade known issues found in `v1.2.0`, we suggest upgrading `v1.1.2` and `v1.2.0` clusters to `v1.2.1`. The known issues found in `v1.2.0` are:
+Harvester `v1.2.1` fixes upgrade known issues found in `v1.2.0`, we suggest upgrading `v1.1.2`, `v1.1.3`, or `v1.2.0` clusters to `v1.2.1`. The known issues found in `v1.2.0` are:
 - [An Upgrade is stuck in the Post-draining state](./v1-1-2-to-v1-2-0.md#9-an-upgrade-is-stuck-in-the-post-draining-state)
 - [An upgrade is stuck in the Upgrading System Service state due to the customer provided SSL certificate without IP SAN error in fleet-agent](./v1-1-2-to-v1-2-0.md#10-an-upgrade-is-stuck-in-the-upgrading-system-service-state-due-to-the-customer-provided-ssl-certificate-without-ip-san-error-in-fleet-agent)