Generic managed service flow - Phase 2

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.

• integrated with the developer catalog & managed service catalog
• enabling the authorization / subscription checks

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 access any "off cluster" service through a consistent flow

Acceptance criteria

1. non-plugin mechanism for contributing catalog items
2. dynamic UI for auth

Dependencies (External/Internal)

Design Artifacts

Exploration

Note