From af9225e21a83ed287a0a04aefa617e44849fa21e Mon Sep 17 00:00:00 2001 From: Josh van Leeuwen Date: Wed, 8 Feb 2023 23:24:31 +0000 Subject: [PATCH] Adds a note about the maximum version skew when upgrading dapr (#3081) * Adds a note about the maximum version skew when upgrading dapr Signed-off-by: joshvanl * Update daprdocs/content/en/operations/hosting/kubernetes/kubernetes-upgrade.md Co-authored-by: Hannah Hunter <94493363+hhunter-ms@users.noreply.github.com> Signed-off-by: Josh van Leeuwen * Update daprdocs/content/en/operations/hosting/kubernetes/kubernetes-upgrade.md Co-authored-by: Hannah Hunter <94493363+hhunter-ms@users.noreply.github.com> Signed-off-by: Josh van Leeuwen * Update daprdocs/content/en/operations/hosting/kubernetes/kubernetes-upgrade.md Co-authored-by: Hannah Hunter <94493363+hhunter-ms@users.noreply.github.com> Signed-off-by: Josh van Leeuwen * Update daprdocs/content/en/operations/hosting/kubernetes/kubernetes-upgrade.md Co-authored-by: Hannah Hunter <94493363+hhunter-ms@users.noreply.github.com> Signed-off-by: Josh van Leeuwen * Update daprdocs/content/en/operations/hosting/kubernetes/kubernetes-upgrade.md Co-authored-by: Hannah Hunter <94493363+hhunter-ms@users.noreply.github.com> Signed-off-by: Josh van Leeuwen * Move skew policy to `support-release-policy.md`, and reference that in the Kubernetes upgrade documentation. Signed-off-by: joshvanl * Update daprdocs/content/en/operations/hosting/kubernetes/kubernetes-upgrade.md Signed-off-by: Mark Fussell --------- Signed-off-by: joshvanl Signed-off-by: Josh van Leeuwen Signed-off-by: Mark Fussell Co-authored-by: Hannah Hunter <94493363+hhunter-ms@users.noreply.github.com> Co-authored-by: Mark Fussell --- .../en/operations/hosting/kubernetes/kubernetes-upgrade.md | 4 ++++ .../content/en/operations/support/support-release-policy.md | 4 ++++ 2 files changed, 8 insertions(+) diff --git a/daprdocs/content/en/operations/hosting/kubernetes/kubernetes-upgrade.md b/daprdocs/content/en/operations/hosting/kubernetes/kubernetes-upgrade.md index c68d54d3b..f62624bc6 100644 --- a/daprdocs/content/en/operations/hosting/kubernetes/kubernetes-upgrade.md +++ b/daprdocs/content/en/operations/hosting/kubernetes/kubernetes-upgrade.md @@ -14,6 +14,10 @@ description: "Follow these steps to upgrade Dapr on Kubernetes and ensure a smoo ## Upgrade existing cluster to {{% dapr-latest-version long="true" %}} There are two ways to upgrade the Dapr control plane on a Kubernetes cluster using either the Dapr CLI or Helm. +{{% alert title="Note" color="primary" %}} +Refer to the [Dapr version policy]({{< ref "support-release-policy.md#upgrade-paths" >}}) for guidance on which versions of Dapr can be upgraded to which versions. +{{% /alert %}} + ### Dapr CLI The example below shows how to upgrade to version {{% dapr-latest-version long="true" %}}: diff --git a/daprdocs/content/en/operations/support/support-release-policy.md b/daprdocs/content/en/operations/support/support-release-policy.md index 91da046f0..310900902 100644 --- a/daprdocs/content/en/operations/support/support-release-policy.md +++ b/daprdocs/content/en/operations/support/support-release-policy.md @@ -72,6 +72,10 @@ The table below shows the versions of Dapr releases that have been tested togeth After the 1.0 release of the runtime there may be situations where it is necessary to explicitly upgrade through an additional release to reach the desired target. For example, an upgrade from v1.0 to v1.2 may need to pass through v1.1. +{{% alert title="Note" color="primary" %}} +Dapr only has a seamless guarantee when upgrading patch versions in a single minor version, or upgrading from one minor version to the next. For example, upgrading from `v1.6.0` to `v1.6.4` or `v1.6.4` to `v1.7.0` is guaranteed tested. Upgrading more than one minor version at a time is untested and treated as best effort. +{{% /alert %}} + The table below shows the tested upgrade paths for the Dapr runtime. Any other combinations of upgrades have not been tested. General guidance on upgrading can be found for [self hosted mode]({{< ref self-hosted-upgrade >}}) and [Kubernetes]({{< ref kubernetes-upgrade >}}) deployments. It is best to review the target version release notes for specific guidance.