The Control Plane node is not tainted

[alpeon]

About

Out of the box deploying the cluster with Rancher the control plane nodes are not tainted and workloads can be scheduled to these nodes.

NAME                                    READY   STATUS    RESTARTS   AGE     IP           NODE                       NOMINATED NODE   READINESS GATES
pod/nginx-deployment-7769f8f85b-699wc   1/1     Running   0          83m     10.42.2.3    capone2-md-0-lnlrq-sg858   <none>           <none>
pod/nginx-deployment-7769f8f85b-84vtk   1/1     Running   0          6m35s   10.42.1.6    capone2-md-0-lnlrq-9r6n7   <none>           <none>
pod/nginx-deployment-7769f8f85b-9xn6d   1/1     Running   0          6m35s   10.42.0.24   capone2-bzmdt              <none>           <none>
pod/nginx-deployment-7769f8f85b-rr88b   1/1     Running   0          83m     10.42.3.3    capone2-md-0-lnlrq-lmpnl   <none>           <none>

NAME                            STATUS   ROLES                       AGE    VERSION          INTERNAL-IP    EXTERNAL-IP    OS-IMAGE             KERNEL-VERSION       CONTAINER-RUNTIME
node/capone2-bzmdt              Ready    control-plane,etcd,master   154m   v1.31.4+rke2r1   172.17.2.204   172.17.2.204   Ubuntu 22.04.5 LTS   5.15.0-140-generic   containerd://1.7.23-k3s2
node/capone2-md-0-lnlrq-9r6n7   Ready    <none>                      125m   v1.31.4+rke2r1   172.17.2.206   172.17.2.206   Ubuntu 22.04.5 LTS   5.15.0-140-generic   containerd://1.7.23-k3s2
node/capone2-md-0-lnlrq-lmpnl   Ready    <none>                      105m   v1.31.4+rke2r1   172.17.2.205   172.17.2.205   Ubuntu 22.04.5 LTS   5.15.0-140-generic   containerd://1.7.23-k3s2
node/capone2-md-0-lnlrq-sg858   Ready    <none>                      105m   v1.31.4+rke2r1   172.17.2.207   172.17.2.207   Ubuntu 22.04.5 LTS   5.15.0-140-generic   containerd://1.7.23-k3s2

Expected

We should apply the NoSchedule taint by default to make sure that pods are not getting scheduled onto the control plane nodes.