Owner: Architect:

David

Story (Required)

As an OpenShift User, I would like to be able to reserve a Cloud Service using Label Selector feature of SBO, so that it is easy to discover Services that can be bound to applications

Background (Required)

ODC support today direct binding an application/workload to a service that is bindable. We will like to also support "Reserving" a service using Label selector feature of SBO. This will allow workloads to se a label in their compute resources and SBO will project the data from the Service automatically.

Glossary

NA

Out of scope

Any Work on SBO

In Scope

Enablement in ODC

Approach(Required)

See this document for some context on user experiences using label selector: https://docs.google.com/document/d/1cot0FWo5ggJASW_Vurwi0-MaduxctM449Wjx7t0rQB0/edit#heading=h.pszbzxrd6lv4
The Idea here is to be able to list Bindable Services and the select them for reservation. A reservation will allow developer to add a label or labels to hold the reservation. This will create a SarviceBinding Resopurce as described in the document. Developer should also be able to search for Reservation which under the covers will mean searching for SBO resources with label selector and then displaying the fields that can be projected to workloads that use that label. See the document for examples on how this is done from CLI.

Demo requirements(Required)

A great demo will demonstrate creating reservations, displaying reservation labels and fields, and deploy compute resources that use the reservation labels. Workloads that use the labels for a service should get the fields identified by the service binding secret mounted on the compute resources.

Dependencies

NA

Edge Case

Removing a reservation means deleting a service binding object. We would not handle the projected data on compute resources that are currently using the labels for reservation.

Acceptance Criteria

Developers can reserve a bindable service
Developers can list reservations
Developers can Remove a Reservation
There are testcases added for reservation above
Documentation: Yes

Upstream: Service Reservation concept would need to be documented in Console project

Downstream: Service Reservation Concept will have to be documented in OpenShift Docs

Release Notes Type: <New Feature/Enhancement/Known Issue/Bug
fix/Breaking change/Deprecated Functionality/Technology Preview>

INVEST Checklist

Dependencies identified

Blockers noted and expected delivery timelines set

Design is implementable

Acceptance criteria agreed upon

Story estimated

v

Legend

Unknown

Verified

Unsatisfied