rancher-docs/archived_docs/en/version-2.5/explanations/integrations-in-rancher/fleet-gitops-at-scale/windows-support.md at 2dcfa6f6b856c19b77dc7cf9f0804d9753fbdc4a

mirror of https://github.com/rancher/rancher-docs.git synced 2026-05-24 05:38:21 +00:00

Files

T

Lucas Saintarbor 8c76072fd2 Archive v2.5 docs (#1634 )

* Update docusaurus.config.js/Remove v2.5 redirects and update v2.5 label and path

* Update version-2.5-sidebars.json with notice

* Remove v2.5 files/Add v2.5 files to archived_docs folder

* Fix broken link

* Fix broken link/typo

* Fix broken links

2025-02-18 14:08:09 -08:00

953 B

Raw Blame History

title

title
Windows Support

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:

Cordon all Windows nodes.
Apply the below toleration to the agent workload.
Uncordon all Windows nodes.
Delete all agent pods. New pods should be created with the new toleration.
Once the agent pods are running, and auto-update is enabled for Fleet, they should be updated to a Windows-compatible agent version.

tolerations:
- effect: NoSchedule
  key: cattle.io/os
  operator: Equal
  value: linux

953 B Raw Blame History

953 B

Raw Blame History