rancher-docs/archived_docs/en/version-2.9/integrations-in-rancher/fleet/windows-support.md at 8c8f8a5f2edec3d7f5abc321e7ca42e681919fdb

mirror of https://github.com/rancher/rancher-docs.git synced 2026-05-25 06:08:29 +00:00

Files

T

Lucas Saintarbor 4a0d71b3f3 Archive v2.9 docs (#2219 )

* Archive v2.9 content files / add archive notice

* Update config / sidebar

* Remove v2.9 redirects

* Fix typo in config

* Update versions listing page

* Fix typo in notice files

* Fix typo in versions listing page

2026-03-04 16:54:35 -08:00

937 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

937 B Raw Blame History

937 B

Raw Blame History