-
Epic
-
Resolution: Obsolete
-
Undefined
-
None
-
None
-
SBO 2.0
-
False
-
None
-
False
-
Not Selected
-
To Do
-
QE Needed, Docs Needed, TE Needed, Customer Facing, PX Needed
-
80% To Do, 0% In Progress, 20% Done
Problem:
SBO servicebinding.io API is already GAed and should be the API of choice in the field. We need to start the depreciation process for core.os API to force this behavior. We also need to keep servicebinding.io API clean of additional features that are not defined in spec.
Goal:
Deprecate the Service Binding object under binding.operators.coreos.com api group.
Why is it important?
Simplify SBO code that we need to maintain and simplify test harness we need to maintain.
Use cases
- ODC should use servicebinding.io API and remove support for CoreOS bindings (APPSVC-1235, APPSVC-1247, APPSVC-1248)
- Users of SBO should get early warning via downstream docs that core.os API is getting deprecated
- Users will only be able to create ServiceBinding CRs under the servicebinding.io API group
- When possible we should automatically migrate ServiceBinding CRs from core.os to servicebinding.io
- BindableKinds CR should stay under core.os api group
Demo requirements
One good demo will be to show ODC creating binding resources under the right API group
Acceptance criteria
(Jan/March 2023) 1.4 (OCP 4.13?)
Capture migration steps from CoreOS API to Spec API (Automated and manual steps) (APPSVC-1249)
Blog intent to deprecate SBO (whats changed, what stays the same, required automated and manual steps required)
Internal communication of deprecation (managed kafka, odo, odc, dbaas)
Visualize spec API service bindings in ODC (propose to ODC with
APPSVC-1253, implement in APPSVC-1247)
Migrate ODC to make spec bindings by default (APPSVC-1248)
Update CoreOS service binding CRD that its deprecated (
APPSVC-1236)
Upstream: Deprecation announcement and migration docs (upstream-docs)
Downstream: Deprecation announcement and migration docs (needs-docs)
Run Conformance test against Spec API (APPSVC-1239)
Disable SBO's ability to install in a single namespace (APPSVC-1062)
(July 2023) 2.0 (OCP 4.15)
Cannot create ServiceBinding Resources under core.os group
Can still see BindableKinds under core.os group
All Test cases have been update to remove test for ServiceBinding under core.os
UI changes required to remove support for CoreOS API (APPSVC-1235)
Support Watch for Label Selector (APPSVC-1112)
(NTH) Render Doc preview on PR (APPSVC-979)