[RFE] Make it easier to discover older versions of Operators in a CatalogSource

[awgreene]

Feature Request

Is your feature request related to a problem? Please describe.
Today it's not possible to install an older version of an Operator unless the user exactly knows the CSV semantic version. Furthermore, no tooling exists that helps users understand the contents of CatalogSources on cluster.

Why is this important:
There are many reasons why a user may not want to choose not to install the latest version of an operator - whether it's lack of testing or known problems. It should be easy for a user to discovers what versions of an Operator OLM has in its catalogs and update graphs and expose this information in a consumable way to the user.

Why is this important to happen on the cluster:
On-cluster catalog inspection can help an admin check:

• If a catalog with known content works correctly on the cluster.
• If certain versions of an Operator have been deprecated.
• If newer z-streams versions of a desired minor versions are available.
• If a certain version got removed.

Describe the solution you'd like

• A user can see list of available versions of an Operator in a channel on the cluster
• A user can see a list of available channels of an Operator on the cluster
• A user can see all available Operators in a particular catalog on the cluster

[stale]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

[stale]

This issue has been automatically marked as stale because it has not had any recent activity. It will be closed in 7 days if no further activity occurs. Thank you for your contribution.
For more help on your issue, check out the olm-dev channel on the kubernetes slack [1] and the OLM Dev Working Group [2] [1] https://kubernetes.slack.com/archives/C0181L6JYQ2 [2] https://github.com/operator-framework/community#operator-lifecycle-manager-wg

[stale]

This issue has been automatically closed because it has not had any recent activity. Thank you for your contribution.

[codihuston]

Just wanted to bump this... for all of the reasons OP listed.