Problem:

Need to determine & implement the support needed for managed services. The support should be for any off cluster managed service.

Things to consider:

• How is an off cluster managed service "identified" so that it can be visualized in topology
• What does an off cluster managed service look like in topology? Does it have a status that needs to be visualized?
• This off cluster managed service should be a valid target for a Service Binding connector
• What information is available in the side panel

NOTE:
Determine if additional extensions need to be added for their support.

Initial high level storyboards shared at CY21 Q1 Planning

ADR-00022 https://docs.google.com/document/d/1fcc8Xz4ccLx6CKK_kpZ7D0cM2nQWGtDGms8FUonZSRo/edit#

Tech Preview for 4.8, GA in 4.9
Associated Operator ... currently called Managed Services Binding Operator (name to change)

=====

Overview

tbd

Exploration Results

Jamboard: https://jamboard.google.com/d/1q2aQAJAF4VLQwVo6enFr6lo2DnizC_ZR3OAjYQ1m7ck/viewer?f=0

Artifacts from Epic Exploration can be found in this drive
– Update this list after Epic Exploration

1. GA feature, thus should be properly documented
2. GA feature, thus need to provide enablement
3. Tech Preview feature, documentation should be stretch goal
4. Tech Preview feature, enablement should be stretch goal
5. Include in what's new RHD blog
6. Consider for stretch RHD blog

Acceptance Criteria

• Display all discoverable managed services to the developer in the developer catalog
• Ability to connect my application to a managed service through the user of a service binding.
• Display all accessible managed services in topology
• Ability to gesture on topology and create a service binding between my application and the managed service