-
Story
-
Resolution: Unresolved
-
Undefined
-
None
-
None
-
8
-
False
-
None
-
False
-
-
Owner: Architect:
_<Architect is responsible for completing this section to define the
details of the story>_
Story (Required)
As an OpenShift user, I'd like to have users migrated to spec bindings away from CoreOS bindings when possible.
Background (Required)
With SBO v2.0, we're deprecating & removing CoreOS service bindings. As a part of the migration process, we should migrate CoreOS bindings to spec bindings when possible. This may be done through a conversion webhook (documentation for which may be found here and here. This won't be a perfect conversion: there are features supported by CoreOS bindings that aren't supported by spec bindings, so this conversion is fallible.
Glossary
<List of new terms and definition used in this story>
Out of scope
In Scope
Convert CoreOS bindings to spec bindings when we can.
Approach(Required)
Investigate: Can conversion webhooks do resource migrations (e.g. CoreOS to spec API namespace)? If so, use a conversion webhook to rewrite CoreOS bindings into spec bindings.
Demo requirements(Required)
A demo should show off how CoreOS bindings are rewritten.
Dependencies
APPSVC-1236 - we should probably mark coreos bindings as deprecated before we start autoconverting them.
Edge Case
The conversion process is fallible. Can conversion webhooks handle this?
Acceptance Criteria
Convert CoreOS bindings to spec bindings.
Test conversion process: passing & failing cases
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