Virtualization Management, support for Harvester extension
Is your feature request related to a problem? Please describe.
The Virtualization Management tab is implemented as a built-in plugin that gives access to the users to the Harvester clusters list.
After importing a new Harvester cluster, the user can click on the cluster name in the clusters list and Rancher reaches out to the Harvester server, loads the Harvester UI code from that server and presents it to the user.
Starting from Rancher 2.10, Harvester will be available as a standard Rancher extension that can be installed from its extension registry although the Virtualization Management page is still built-in.
As a result of above, users will have to manually install the new extension to have access to the Harvester clusters.
Describe the solution you'd like
We need to inform the users to add the Harvester extension registry and install the new extension.
-
Harvester extension is not installed:
- Display view 1. even if the cluster list is not empty.
- Keep the current presentation layout.
- Disable or remove the 'Import Existing' button if the Harvester extension is not installed.
- Remove the empty list label.
- Add guidelines on how to install the Harvester extension in case of the Harvester extension is not installed.
- If the user doesn't have permission to install extensions, add guidelines to request the extension to the admin.
-
Harvester extension is installed:
- Display view 2. - empty list or the list of clusters.
- 'Import Existing' button is enabled.
Describe alternatives you've considered
Changes described here are the minimum step to integrate the Harvester extension. We will need to define a more efficient workflow to install and use the extension.
Additional context
just added the label area/extensions and I subscribed to keep track of this as well 🙏
@torchiaf we're past feature complete for 2.10.0 but does this need to get in for that version? @nwmac do we need to add this to our grooming session tomorrow?
@gaktive we need to do this, so yes, we need to discuss