This message was deleted.

the newer provisioning framework does not work like that any more. It doesn’t SSH in and run stuff. It is entirely built around generating cloud-init config that instructs the node to run scripts to install the rancher system agent from the rancher server.

Ok. The SSH key I mentioned is also used to authenticate in order to spin up a VM on Triton. Anyway, the latest Rancher node driver docs still mention implementing node drivers based on rancher machine so shouldn’t my driver still work? Looking for how to get past the credential aspect… Also, can you link me to any rancher cloud init docs? Thanks.