Incomplete UI for RKE2/K3s Cluster Creation via Rancher Manager in Open Telekom Cloud

[Wolfslicht]

Description
When attempting to create RKE2/K3s clusters via the Rancher Manager UI for the Open Telekom Cloud, the UI does not provide fields for "Secret Key," "Project," or "region" after activating the node driver for Open Telekom Cloud. This issue prevents the completion of the cluster creation process as these fields are essential for establishing a connection to the Open Telekom Cloud.

Expected Behavior
The UI should provide input fields for "AccessKey," "Secret Key," "Project," and "region" when creating RKE2/K3s clusters via Rancher Manager.
Users should be able to input their credentials and details to successfully create RKE2/K3s clusters in the Open Telekom Cloud.

Current Behavior
Upon reaching the step to input Open Telekom Cloud credentials, the UI only displays an input field for "AccessKey."
The absence of fields for "Secret Key," "Project," and "region" makes it impossible to proceed with the cluster creation.

Steps to Reproduce

1. In Rancher Manager, navigate to the section for activating drivers and activate the Node Driver for Open Telekom Cloud.
2. Confirm that the Node Driver is activated.
3. Go to the "Create New Cluster" section under RKE2/K3s and select "Open Telekom Cloud."
4. Observe the incomplete UI, which only shows an input field for the "AccessKey" and lacks fields for "Secret Key," "Project," and "region."

Attached Screenshot
Driver

UI of Create RKE2/K3S Open Telekom Cloud

Cloud Cred Creation Page

Possible Cause
The issue may stem from a UI bug or an incomplete integration of the Open Telekom Cloud node driver with the Rancher Manager UI, leading to missing input fields for essential configuration details.

Requested Information

• Any available workarounds that allow for the manual or alternative specification of the missing fields to proceed with cluster creation.
• Timeline for a fix or update to address this UI issue and provide a complete form for Open Telekom Cloud cluster creation.

[curx]

@Wolfslicht
Do you have set the node driver to disable and afterward reable it again, to fix the issue?

[Wolfslicht]

Hey @curx,

I tried this on a fresh installed Rancher Manager, and also with disable and re-enable.
Sadly the behavior stays the same.