Problem:

Today, developers are constrained/limited to the set of operator backed services which are enabled by the administrator by installing operators from Operator Hub.

Currently, developers are able to view Installed Operators, although unsure if that's needed.  They do not have the ability to view, request or deploy available Operators in the Operator Hub.

Goal:

We'd like to enable self-service for developers.

Why is it important?

Use cases:

1. As a developer, I'd like to be able to discover operator backed services, regardless if operators are currently installed.
2. As a developer, I'd like a way to create an operator backed service, whether or not the operator is installed.

Acceptance criteria:

1. <criteria>

Dependencies (External/Internal):

Design Artifacts:

Peter's WIP Design

Exploration:

Providing a request mechanism is not recommended. This will cause even more tickets to be opened for admins to deal with.

Explore the possibilities of having the admin provide an "approved list" of operators. These operators wouldn't have to be installed by the admins. Operator backed services which are "unlocked" by approved operators which are not yet installed, will be available in the developer catalog. When the user selects that service, the operator would need to be installed in the background (without making the developer have to provide input), before the service is installed.

Note:

Peter Kreuser has been exploring these possibilities and having discussions with Serena & Tony.