Owner: Architect:

_<Architect is responsible for completing this section to define the
details of the story>_

Story (Required)

As a part of the deprecation process for CoreOS bindings, we need to move our users toward spec bindings. ODC is one of our high-impact users, and we need to migrate their usage as well.

Background (Required)

With the release of SBO 2.0, we're going to remove support for CoreOS bindings (they'll be deprecated in SBO 1.4). We should move our users away from CoreOS bindings where we can.

Glossary

<List of new terms and definition used in this story>

Out of scope

Other users of SBO will be addressed in separate stories. The removal of CoreOS bindings within SBO will happen in a separate story.

In Scope

For this story, only remove support for CoreOS bindings from ODC.

Approach(Required)

• Remove visualizing CoreOS bindings from ODC.
• Remove the ability to create new CoreOS bindings from within ODC.

Demo requirements(Required)

• CoreOS bindings should not be visualized in ODC.
• CoreOS bindings should not be available when creating a binding.

Dependencies

• APPSVC-1247

Edge Case

Are there features used in CoreOS bindings not supported by spec bindings that ODC uses?

Acceptance Criteria

CoreOS binding support should be removed.

Development:

QE:
Documentation: Yes/No (needs-docs|upstream-docs / no-doc)

Upstream: <Inputs/Requirement details: Concept/Procedure>/ Not
Applicable

Downstream: <Inputs/Requirement details: Concept/Procedure>/ Not
Applicable

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