Goal: Switch over Quarkus-based deployment to CR-based and also provide basic runtime views

Architecture brief:

• Move away from quarkus deployment towards CRD deployment
• We should be able to deploy the workflow + supporting files (application.properties, OpenAPI files)
• User should be able to access a runtime view per deployment 
• Users should be able to start a workflow using a forms rendered in a endpoint (besides embedded on dev ui)
• The current baseline should be at least less than the MVP 0: 30 seconds for first deploy, 5 seconds for hot-reload, for 10 simultaneous users and 100 users/day
• …

Stretch Goals

• Dashboards for Workflow Visualization + Deployment Metrics
• ..

Points to discuss

• How send a workflow to CR? REST endpoint POST? ZIP file (wf + resources)? Github fetch?
• Are we going to support sub workflows?
• Can we release without user auth? How are we going to deal with scale ? 2 deployments?

Blockers

• Install operator on operate first

• ..

Deliverables

• an internal kubesmarts deployment URL, able to author a single file example and deploy below the target baseline

• a recording demoing this MVP

• A presentation of this MVP for our community