Epic Goal

• When installing OpenShift Pipelines, the console is "enhanced" with our shipped UI

Why is this important?

• This should help us ship full-featured features where the UI is also up-to-date with the API
• This would give us ownership on our UI

Scenarios

N/A

Acceptance Criteria (Mandatory)

• CI - MUST be running successfully with tests automated
• Release Technical Enablement - Provide necessary release enablement details and documents.
• Installing OpenShift Pipelines brings our own UI

Dependencies (internal and external)

• https://issues.redhat.com/browse/SRVKP-2661 — Our own operator

Previous Work (Optional):

• https://docs.google.com/presentation/d/1YS-1UL4Ijr4EuuKTOIWQrGLKW099pa2tdiZ2VS7aBKE/edit#slide=id.g11a0edd5cc4_0_0

Open questions::

• Can a dynamic plugin "override" / "shadow" the built-in console parts ?

Done Checklist

• Acceptance criteria are met
• Non-functional properties of the Feature have been validated (such as performance, resource, UX, security or privacy aspects)
• User Journey automation is delivered
• Support and SRE teams are provided with enough skills to support the feature in production environment