Problem:

In 4.6, we have 7 quick starts which are shipped as part of the console. There's no way for an operator or a customer to provide their own quick starts.

Goal:

The goal Is to provide a mechanism for an operator or customer to extend the console quick start library via a customer resource. This epic is focused on updating the current quick start UI feature to utilize the new extension mechanism documented here.

Requirements

1. Quick starts provided by the console should be available by default
2. Quick starts provided by the console should be able to be removed by cluster admin
3. An operator can extend the console quick start library by creating their own quick starts custom resource
4. A customer (admin) can extend the console quick start library by creating their own quick starts custom resource

Acceptance criteria

1. As a cluster admin, I should see the operator install quick starts for serverless and pipelines
2. As ANY user, I should see the 3 sample app quick starts
3. As ANY user, I should see the Install Serverless App quick start, only if the Serverless Operator is installed
4. As ANY user, I should see the Create App using a Pipeline quick start, only if the Pipelines Operator is installed

Dependencies (External/Internal)

1. Extension work being done by Jakub : Quick Starts for Console Enhancement Proposal
2. Conversion of existing 4.6 quick starts to CRs (5 delivered by console, 1 delivered by Serverless, 1 delivered by Pipelines)

Slack Channel

#tmp-quick-starts in CoreOS Slack instance

Note2