Goal 

• As an admin, I want to enable my end-user developers to be able to self-service themselves to install and make use of operators I add to a pre-approved list. I want to be able to specify details about how the operator will be installed (Channel/version, namespace, etc) in advance so the developer doesn't have to deal with these details when they install it.
• As a developer, I want to be able to easily discover useful operands of operators that are available to me (but maybe not yet installed) and have the operator be easily (if not quickly) installed so I can use them.
• Admins should be able to create a list of pre-approved operators that developers can discover and install themselves, and admins can specify details of that install in advance
  • Operators that require some operand be created might have a harder time with this
• Developers can see the operands of these pre-approved operators in their dev catalog, and upon selecting to use them, can be guided through the install process with values pre-filled by the admin. Once the operator is installed the developer can be taken to create an instance of the operand they initially discovered. 

Background 

• This story was spun off of the 'blue sky' idea (PD-687) of allowing developers to request admins install operators for them. During examination of that design it was determined that admins field enough requests already, and it would be better if developers could self-service.

Outcome- definition of done

• Create a high level design that conveys this idea
• Share with stakeholders from Admin, Dev, and OLM
• Create final design story
• Also: Share at feedback sessions
• Link Design Doc

UX Design: https://docs.google.com/document/d/1V_zBuV_ZbixXtjaNruJxsuR_QSJoqsZ3a7OSPDnCPUQ/edit?usp=sharing