Goal

Adi Admin is able to create a shared multi-cluster environment that an application workspace can deploy apps onto. See slides 5 & 6 of the Adi Admin 2022 story.

Workspace creation - based on KCP

https://miro.com/app/board/o9J_lrN5Ij0=/?moveToWidget=3074457366591016178&cot=14

https://docs.google.com/document/d/1qa3vV0feGkI23VZPvbTXABuJzkitbttQgYPG662dH6s/edit?usp=sharing

User journey around architect creating and managing a workspace.

User Goal
As an Architect, I want to create a workspace and manage the workspace team.

Why is this important?

Use cases

As an administrator, I need to:

Architecture Overview

Acceptance criteria

Out of scope

• Providers beyond ROSA won’t be available by Summit 2022, but should still be considered as part of the design
• Environments backed by RHEL/Edge devices won’t be supported by Summit 2022, but is a discussion worth having with stakeholders
• For now we can skip an embedded OperatorHub/Catalog browsing step to add operators & services; this can be done via the policy mechanism instead

Dependencies

• KCP architectural acknowledgement
• ACM/Multi-cluster Engine operator considerations, a plan for this to be enabled on-prem too