Goal 

• Users may want to install an older version of an operator for various reasons, including the latest version having limited testing or known vulnerabilities. Today this is only possible if the user knows the exact CSV semantic version of the older version they’d like to install (which isn’t surfaced through any API) and needs to edit YAML to install it.

• Users should be able to use the OperatorHub UI to browse the various versions of an operator across any channels it may have, and view the metadata for that version, and then be able to select the exact version (including older versions) that they’d like to install.

• Allow users to view all versions of an operator across all of its channels, and allow selection of one to view that versions metadata, along with the option to install it.

Background 

• https://operatorhub.io/ has nearly this exact feature already, with regards to selecting a channel, then version, to view that versions metadata

Outcome- definition of done

• Incorporate feedback from high level design story 
• Review with all relevant stakeholders including [tag designers of other products, devs, pms … ]
• If future facing then post to github (4.x) for customer facing feedback
• If targeting a release, ensure “proposed release” field is accurate and ensure final design story is open to the public

Outdated Design Doc: https://docs.google.com/document/d/1_D-TPOremjpCPXZ7hBmNvCrwPU7ISdMuvjwjMiSzlWY/edit?usp=sharing 

UX Design: https://github.com/openshift/openshift-origin-design/pull/515