This message was deleted.

We worked it out, and it was because our Ansible playbook was not cleaning up the nodes correctly, uninstalling just the system agent and not the RKE2 server. Thus, when creating a cluster, it selected the defaults because the configuration file was missing. I assume, if specific directories and binaries are in place, RKE2 must not wait for the new configuration file to be updated before the startup process begins