-
Epic
-
Resolution: Can't Do
-
Undefined
-
None
-
None
-
Distribution of SBO with OLM
-
False
-
False
-
To Do
-
QE Needed, Docs Needed, TE Needed, Customer Facing
-
0% To Do, 0% In Progress, 100% Done
-
Undefined
Problem
To remove the adoption barrier of discovering and installing SBO, we should make it available by default on OpenShift.
Description
The work on this epic will be to align with the requirements from OLM and work on getting SBO enabled with OLM.
Related to upstream alignment, there is a working group for "Service Bindings". Right now, the effort is around writing an official specification for binding services to k8s applications. As a part of the working group, there are contributions from VMWare, IBM and us (other people also joined the party from time to time). The intention is to push the specification under Service Catalog SIG.
From the latest discussion, it's highly possible that the working group will also come with a default implementation proposal - but we are not yet there.
Taking that into consideration, we should look at how best to enable SBO with OLM and for that the approach of SBO having its own operator in project seems reasonable.
Acceptance Criteria
- SBO is available out of the box when installing OCP, OSD, CRC
- OKD would be nice, but not sure OLM is there by default
Security
- Need to investigate security (Matt Miller) implication
- is blocked by
-
-
- Closed
-
- is related to
-
OCPPLAN-9555 Platform Operators
-
- In Progress
-