From b75006c45983dc61952493fd1f48e42956287b03 Mon Sep 17 00:00:00 2001 From: Nick Gerace Date: Tue, 9 Feb 2021 14:55:12 -0500 Subject: [PATCH 1/2] Add 2.5.6 Fleet upgrade workflow for Windows --- .../en/deploy-across-clusters/fleet/_index.md | 21 ++++++++++++++++++- 1 file changed, 20 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 a794ffbe459..15759776283 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 @@ -19,10 +19,29 @@ deploy everything in the cluster. This give a high degree of control, consistenc Fleet comes preinstalled in Rancher v2.5. To access it, go to the **Cluster Explorer** in the Rancher UI. In the top left dropdown menu, click **Cluster Explorer > Continuous Delivery.** On this page, you can edit Kubernetes resources and cluster groups managed by Fleet. +### Windows Support + +Prior to Rancher v2.5.6, the `agent` would fail on downstream clusters with Windows nodes. +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. +1. Apply the below toleration to the `agent` workload. +1. Uncordon all Windows nodes. +1. Delete all `agent` pods. New pods should be created with the new toleration. +1. Once the `agent` pods are running, and auto-update is enabled for Fleet, they should be updated to a Windows-compatible `agent` version. + +```yaml +tolerations: +- effect: NoSchedule + key: cattle.io/os + operator: Equal + value: linux +``` + ### GitHub Repository The Fleet Helm charts are available [here.](https://github.com/rancher/fleet/releases/latest) ### Documentation -The Fleet documentation is at [https://fleet.rancher.io/.](https://fleet.rancher.io/) \ No newline at end of file +The Fleet documentation is at [https://fleet.rancher.io/.](https://fleet.rancher.io/) From 4ceee3331181b0df90eaa55c61abf1bead898fa9 Mon Sep 17 00:00:00 2001 From: Nick Gerace Date: Thu, 11 Feb 2021 13:02:19 -0500 Subject: [PATCH 2/2] 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.