You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Are there any additional port requirements when using Windows nodes in an RKE2 cluster?
Document why DSR is enabled by default on a RKE2 Windows worker and why it cannot be disabled (DSR provides scaling benefits, Calico requires DSR being enabled, etc)
Document DNS limitations in RKE2 clusters compared to RKE1 clusters (internal DNS server may be required for some environments)
Document that dual-stack is NOT supported for Windows Server and cannot be enabled on RKE2 cluster with Windows workers (we don't stop a user from enabling dual stack but it will not work on the Windows nodes)
Document how to use nodes electors/node affinities when scheduling workloads
Document that RKE2 Windows does not make use of RKE1 Windows taints/tolerations
Document Supported Calico Configuration (no BGP, no ipipMode, etc)
2.6.5 Release Notes:
v1.21.x of RKE2 will remain experimental and unsupported for RKE2 Windows
When upgrading Windows nodes in RKE2 clusters via the Rancher UI, Windows worker nodes will require a reboot after the upgrade is completed.
Further items to document and release note:
RKE2 provisioning GA for Windows will only support v1.22 and up of RKE2
Document/Release note Windows Server 2022 issues with nodeports
The text was updated successfully, but these errors were encountered:
this issue will track docs items/tasks that were bumped from 2.6.4 #150
Three Major Features to Document for 2.6.5:
gMSA (experimental)
Windows Support for RKE2 vSphere Node Driver Clusters
PNI for Calico in RKE2 Windows Clusters
General Documentation:
2.6.5 Release Notes:
Further items to document and release note:
The text was updated successfully, but these errors were encountered: