Owner: Architect:

Andy Sadler

Story (Required)

As an OpenShift user, I would like to understand the feature difference between the CoreOS and Spec service bindings.

Background (Required)

As a part of the deprecation process for the CoreOS service binding resource, we need to understand what features aren't available anymore. We currently have an ad-hoc understanding, but a categorization of this needs to be documented and understood.

Glossary

• CoreOS service bindings: servicebindings.bindings.coreos.com resources.
• Spec service bindings: servicebindings.servicebinding.io resources.

Out of scope

This story is all about identifying & documenting the gap. Steps to bridge the gap are not relevant for this story.

In Scope

Documenting & understanding what features exist in CoreOS service bindings that don't exist in the specification.

Approach(Required)

Methodically identify the features in CoreOS service bindings and Spec service bindings.  What can we do using CoreOS that we can't using the Spec?

Demo requirements(Required)

Not relevant: no demo makes sense for this story.

Acceptance Criteria

• A list of features available in CoreOS service bindings but not in Spec service bindings

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