Goal:

Convert Serverless from a static to a dynamic plugin, while keeping it in the mono repo (thus the delivery mechanism will remain the same).

All internal dependencies should be identified and evaluated to see what needs to be supported by the SDK. Once this epic is complete, the Serverless plugin should no longer have any internal dependencies.

Why is it important?

Our end goal is to have a fully featured SDK which supports dynamic plugins. In the future, we hope to have the Serverless dynamic plugin be delivered via the operator to (a) minimize dependencies between the operator and console and (b) enable users to get access to the pipeline UI bits as the operator and features are enabled rather than waiting for the next OpenShift release.

Acceptance criteria:

SHIPPING work
This work needs to be done above as part of operator (This is a collaboration work with respective operator team). This comprises of below tasks:

1. Needs to finalize on logistics i.e should the UI code be in a new repo / operator repo, workflow and review process going forward
2. e2e tests enablement
3. co owned by ODC/Operator team
4. health check/metrics/monitoring anything else required as part of shipping UI chunks as console plugin via operator’s

Dependencies (External/Internal):

Note: