Allowing non-cluster administrators to manage their Operator subscription

1. Proposed title of this feature request

Allowing non-cluster administrators to manage their Operator subscription

2. What is the nature and description of the request?

A customer wants to allow users to be able to manage their operator subscriptions in their namespaces so they can use the upgrade strategy (manual/automatic) and if the manual, upgrade their own operator installations.

We have a document[1] that describes the configuration for allowing non-cluster administrators to install Operators in their namespace. But, this configuration allows installing operators only through CLI. The customer wants the user to install/manage the operator's subscription through openshift console.

This configuration[1] does not allow to do it through the console. The 'Subscription' tab is missing from the console.

3. Why does the customer need this? (List the business requirements here)

The customer wants project-admin to be able to manage upgrades on already installed operators in their own namespaces.

[1] https://docs.openshift.com/container-platform/4.5/operators/admin/olm-creating-policy.html

Slack Discussion: https://coreos.slack.com/archives/C3VS0LV41/p1608128922311200