Rancher Windows Cluster

Rancher can provision a Windows cluster with combination of Linux worker nodes and Windows worker nodes. For more information on the Rancher Windows cluster, see the official Rancher documentation.

In a Rancher Windows cluster, all Linux worker nodes are:

  • Tainted with the taint cattle.io/os=linux:NoSchedule

  • Labeled with kubernetes.io/os:linux

After SUSE Storage is deployed, you can launch workloads that use SUSE Storage volumes only on Linux nodes.

Deploy SUSE Storage With Supported Helm Chart

You can update the Helm value global.cattle.windowsCluster.enabled to allow SUSE Storage installation on the Rancher Windows cluster.

When this value is set to true, SUSE Storage will recognize the Rancher Windows cluster then deploy SUSE Storage components with the correct node selector and tolerations so that all SUSE Storage workloads can be launched on Linux nodes only.

On the Rancher marketplace, the setting can be customized in customize Helm options before installation:
Edit Options > Other Settings > Rancher Windows Cluster

Also in:
Edit YAML

global:
  cattle:
    systemDefaultRegistry: ""
    windowsCluster:
      # Enable this to allow Longhorn to run on the Rancher deployed Windows cluster
      enabled: true

Set Up SUSE Storage Components For Existing SUSE Storage Deployment

You can set up the existing SUSE Storage when its not deployed with the supported Helm chart.

  • Since SUSE Storage components can only run on Linux nodes, you need to set the node selector kubernetes.io/os:linux for SUSE Storage to select the Linux nodes. For more information, see Node Selector.

  • Since all Linux worker nodes in a Rancher Windows cluster have the taint cattle.io/os=linux:NoSchedule, you must set the toleration cattle.io/os=linux:NoSchedule to allow SUSE Storage to run on those nodes. For more information, see Taint Toleration.