This message was deleted.
# general
a
This message was deleted.
g
I'm experiencing the same thing for a different cloud provider. Did you get this resolved?
@breezy-umbrella-46432 I've been digging into this for my custom node driver as well and I found that if you enable the
addCloudCredentials
field on the node driver in the Rancher API (
/v3/nodeDrivers/<driver_id>
) then the Create RKE2 Cluster screen allows you to enter cloud credentials. However, I think you need to add additional annotations to the driver to tell Rancher which fields in the driver should show up on the dynamically generated "enter cloud credentials" screen as outlined https://extensions.rancher.io/extensions/usecases/node-driver/about-drivers#driver-binary. You can do all this by going to
Cluster Management
>
Drivers
>
Node Drivers
> click the 3 dots next to your custom driver >
View in API
>
Edit
. Hope this helps.
What might also be related is that I had to rebuild my node driver with
export CGO_ENABLED=0
as suggested in https://github.com/rancher/rancher/issues/11339#issuecomment-2122747151.