diff --git a/docs/upgrade/automatic.md b/docs/upgrade/automatic.md index 3d68a0cd11f..e67e87582e4 100644 --- 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 index 5078d3d32a5..948d0bcc104 100644 --- 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" --- @@ -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 index e5d6586aca9..f5da3267885 100644 --- 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 index e2fc3318a31..0d0a469c7ab 100644 --- 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" --- @@ -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 index 3d68a0cd11f..e67e87582e4 100644 --- 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 index 5078d3d32a5..948d0bcc104 100644 --- 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" --- @@ -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)