Hi all, I am using Rancher to manage my RKE2 clust...
# windows
m
Hi all, I am using Rancher to manage my RKE2 clusters. However, if I want to add a Windows node to the cluster, I have to do a few manual adjustments to the Add-On config of Calico before the CNI works only on the Windows nodes. I have to manually update the
serviceCIDRs
of the Calico installation resource (I use
172.17.0.0/18
), set
calicoNetwork.windowsDataplane
to
HNS
, and enable the Calico API Server. Also, it seems like the Windows node container images for Calico are not mirrored like the Linux images, so I have to update the
imagePath
and
imagePrefix
in the installation as well to use the official Calico images. Additionally, a
kubernetes-services-endpoint
ConfigMap has to be created that points to the kube-api-server (which is a bit inconvenient, as we normally connect through the Rancher proxy, which is behind an LB, so we do not have an LB for the kube-api-server in the managed clusters). It is also inconvenient that the whole Add-On configuration that we set in Rancher is sometimes being reset whenever we upgrade the Kubernetes version of the managed cluster. All in all, it works and I can work around it, but it feels kind of wrong having to do so many manual settings (and them being reset upon k8s update) of what seemingly is being done automatically for Linux. If I look at the official documentation for Rancher, none of these steps are also listed, so I assume that this is not the expected experience as well. Does anyone else have to do the same things for their clusters, or am I just doing something wrong?