I think this is a little different. The article assumes you have control over the upgrade process. When you update the cluster config for an RKE2 cluster, rancher automatically replaces nodes 1 by 1 without user intervention. The workaround would be to keep the same name of the template when replacing it, but once you adjust cpu or memory, it’ll start auto replacing nodes. This gives you no time to do manual cordoning and draining.