Hi Folks, we're trying to deploy RKE2 using the IO...
# rke2
g
Hi Folks, we're trying to deploy RKE2 using the IONOS Cloud node driver https://github.com/ionos-cloud/docker-machine-driver/tree/master Works perfectly fine with public nodes, however what we need are private-only nodes, to which Rancher will not have SSH access. We already deploy such, but using custom Terraform modules which bootstrap RKE with cloud-init. Using the driver, we get:
Waiting for SSH to be available...
so it seems the provisioning needs to happen with SSH. Is it an inherit way of how the machine drivers work, or can we somehow achieve cloud-init only provisioning?
update: I've found such piece of code https://github.com/rancher/machine/blob/04e3bd3ab4ff6f81d06a3343b4fc755a657ecddf/libmachine/drivers/drivers.go#L112 suggesting that possibly the machine driver needs to implement the right flags for the detection of cloud init capability to happen?
at least looking for suggestion if i'm looking into the right direction and if it can be possible to make provisioning SSH-less. then we could possibly try forking the driver mentioned
b
The system agent also installs via cloud-init, but you can override and/or merge that config with these lines:
Copy code
#cloud-config

      merge_how:
       - name: list
         settings: [replace]
       - name: dict
         settings: [replace]
This basically says that any config you place in this cloud-init config will replace any other cloud-init configs that have been set.
sorry, I don't know anything about the IONOS Cloud node driver.