public/rancher-docs
1
0
Fork 0
mirror of https://github.com/rancher/rancher-docs.git synced 2026-09-26 13:08:11 +00:00
Code Issues Packages Projects Releases Wiki Activity

Add 2.5.6 Fleet upgrade workflow for Windows

Browse Source
This commit is contained in:
Nick Gerace
2021-02-09 14:55:12 -05:00
parent fd5dfa3457
commit b75006c459
1 changed files with 20 additions and 1 deletions
Download Patch File Download Diff File Expand all files Collapse all files
content/rancher/v2.x/en/deploy-across-clusters/fleet/_index.md
+20 -1
View File
@@ -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/)
The Fleet documentation is at [https://fleet.rancher.io/.](https://fleet.rancher.io/)