Customize parameter visibility in user cluster creation flow

[csengerszabo]

Description of the feature you would like to add / User story

As a platform admin,
I want to control which options are visible and available during the user cluster creation flow,
so that I can simplify the process and restrict users from selecting certain configurations that are not needed or desired.

Solution details

• Visibility Control: These options should be configurable by the platform admin and not visible to user cluster owners if removed.
• Parameters to control:
  • Remove CNI Options: Ability to remove Canal and None as selectable CNI options during user cluster creation.
  • Remove SSH Keys: Option to hide the SSH keys step from the user cluster creation process.
  • Remove Applications Step: Option to remove the entire Applications step from the creation flow.
  • Remove Static Network Configuration: Allow the admin to hide the Static Network Configuration option.
  • Remove VM Template Selection: Option to prevent the user from selecting a VM Template.
  • Remove Anti Affinity Option: Allow the admin to remove the Anti Affinity option from the flow.

Alternative approaches

Use cases

• The goal is to streamline the cluster creation experience for users by hiding unnecessary or restricted options.

Additional information

[csengerszabo]

/label customer-request
/label sig/api
/label sig/ui

[csengerszabo]

/transfer dashboard

[judge-red]

We would like to request additional parameters to be controlled:

• Remove expose strategies: options to hide each expose strategy individually (and if all are hidden, the drop down should be hidden as well and the default should be used)
• Remove UC Logging and UC Monitoring toggles: option to hide either or both (but the default defined in the admin settings should still be used)
• OpenStack settings: remove availability zone: option to hide the availability zone selection

Explanations:

• The reason why several expose strategies exist is clear, all have clear benefits and drawbacks. But I think there are also many use cases where one of them is undesirable, or where one is clearly the best or even only suitable choice.
• We don't have UC MLA deployed and we have both "enforced" to "disabled", but this still leads to questions as some users are curious about this feature upon seeing the options.
• We only have one availability zone in OpenStack, which is the default AZ, so no need to select it. This is another one that leads to questions despite there effectively only being one choice (since "" and "nova" have the same outcome but are separate choices in the UI).