Generic managed service flow - phase 1 - topology

Problem

With the RHOAS Operator, we have introduced a managed service flow. We need to provide a mechanism to support a consistent user flow for all managed services.(Red Hat and non Red Hat)

• topology representation
• support of SBO

Goal

Provide a generic managed service flow which supports Azure & IBM Managed services

Why is it important?

Use cases

1. Developer should be able to easily identify any off-cluster items which are part of their application/project via topology
2. Developer should be able to easily link off-cluster items with other parts of their application/project

Acceptance criteria

1. Display bindable external services in topology as a trapezoid
2. Users can create binding connections to any bindable external service

Dependencies (External/Internal)

Design Artifacts

Exploration

Note