Currently, generating a ClusterExtension to install an Operator via OLMv1 involves several manual opm commands to identify the correct bundle and version from the catalog. We propose enabling this functionality directly in the OperatorHub UI, allowing users to generate and apply a ClusterExtension for a chosen Operator version directly from the Web Console.

Why does we need this? 

• Streamlines the OLMv1 Operator installation process.

• Eliminates need for CLI knowledge and catalog bundle parsing.

• Reduces operational overhead and time to deployment.

• Enhances self-service capabilities for less experienced users.