swift-sunset-4572
06/16/2023, 8:30 AMCluster API
RKE2 is built on the Cluster API framework, which affects the way cluster configurations are managed and changes are made. Unlike RKE1, RKE2 clusters are more susceptible to node reprovisioning when changes are made to the cluster configuration. This behavior is controlled by the CAPI controllers and not by Rancher itself. Certain changes, such as enabling drain before delete or scaling down the number of nodes, may result in the deletion of existing nodes and the creation of new ones. This is a known issue in the Cluster API that will be fixed in a future release, and Rancher will update the documentation accordingly.
I just want to know whether this issue is resolved in 2.7.4 ?? or is there any workaround to prevent the reprovisioning? Any suggestions and the guidance will be appreciated.