You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The README documents how to configure this node driver via a Kubernetes manifest but Rancher supports configuring a node driver via its user interface. However, when the user interface is used a random ID is generated for the node driver which prevents node driver from being used to create Kubernetes clusters.
A maintainer wrote rancher/rancher#48527 (comment) on the upstream issue and the links within show that the bug has been long-standing for over 2 years with no clear sign of being fixed given there's a workaround using kubectl which is already described in this repository's README.
The README documents how to configure this node driver via a Kubernetes manifest but Rancher supports configuring a node driver via its user interface. However, when the user interface is used a random ID is generated for the node driver which prevents node driver from being used to create Kubernetes clusters.
See the upstream issue rancher/rancher#48527 for more information.
The text was updated successfully, but these errors were encountered: