From 4ceee3331181b0df90eaa55c61abf1bead898fa9 Mon Sep 17 00:00:00 2001 From: Nick Gerace Date: Thu, 11 Feb 2021 13:02:19 -0500 Subject: [PATCH] Add 2.5.6 Fleet upgrade workflow for Windows --- content/rancher/v2.x/en/deploy-across-clusters/fleet/_index.md | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/content/rancher/v2.x/en/deploy-across-clusters/fleet/_index.md b/content/rancher/v2.x/en/deploy-across-clusters/fleet/_index.md index 15759776283..2bfe608fa13 100644 --- a/content/rancher/v2.x/en/deploy-across-clusters/fleet/_index.md +++ b/content/rancher/v2.x/en/deploy-across-clusters/fleet/_index.md @@ -21,7 +21,8 @@ Fleet comes preinstalled in Rancher v2.5. To access it, go to the **Cluster Expl ### Windows Support -Prior to Rancher v2.5.6, the `agent` would fail on downstream clusters with Windows nodes. +Prior to Rancher v2.5.6, the `agent` did not have native Windows manifests on downstream clusters with Windows nodes. +This would result in a failing `agent` pod for the cluster. If you are upgrading from an older version of Rancher to v2.5.6+, you can deploy a working `agent` with the following workflow *in the downstream cluster*: 1. Cordon all Windows nodes.