From fc89c0ddc73afc81d5bcd62624029c09f352d624 Mon Sep 17 00:00:00 2001 From: Jennifer Travinski Date: Mon, 31 Jan 2022 18:18:38 +0000 Subject: [PATCH] Updated note per feedback --- .../rke-clusters/windows-clusters/_index.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/content/rancher/v2.6/en/cluster-provisioning/rke-clusters/windows-clusters/_index.md b/content/rancher/v2.6/en/cluster-provisioning/rke-clusters/windows-clusters/_index.md index 59f9a1c75ed..0374c709e68 100644 --- a/content/rancher/v2.6/en/cluster-provisioning/rke-clusters/windows-clusters/_index.md +++ b/content/rancher/v2.6/en/cluster-provisioning/rke-clusters/windows-clusters/_index.md @@ -43,7 +43,7 @@ The RKE2 provisioning tech preview also includes installing RKE2 on Windows clus Windows Support for RKE2 Custom Clusters requires choosing Calico as the CNI. ->**Important:** Rancher will allow Windows workload pods to deploy on both Windows and Linux worker nodes by default. When creating mixed clusters in RKE2, you must taint the Linux node to ensure Windows workloads will only be deployed to Windows nodes. Refer [here]({{}}/rancher/v2.6/en/logging/taints-tolerations/) for more information on taints and tolerations in Rancher. +>**Important:** Rancher will allow Windows workload pods to deploy on both Windows and Linux worker nodes by default. When creating mixed clusters in RKE2, you must edit the NodeSelector in the chart to direct the pods to be placed onto a compatible Windows node. # Requirements for Windows Clusters