DevWorkspace engine MVP

[l0rd]

Is your enhancement related to a problem?

That's a list of subtasks required for the DevWorkspace Engine MVP

Subtasks

• Change defaults of chectl/che-operator in case of DevWorkspace
• Projects clone should happen before other components are started
• Project is not imported when using devfile v2 factory flow Project is not imported when using devfile v2 factory flow #19371
  • che-server API should return the git repo details along with original devfile content Provide scm info in factory v2 che-server#5
  • dashboard should infer the project details in the original devfile object
• Release devfile spec v2.1 (milestone), Che side subtasks:
  • Commands scoped to a project
  • Extending DevWorkspace Status fields
  • Root folders for projects
• Support starting devfile v2 based workspaces on Kubernetes (not OpenShift) <-- OUT OF SCOPE OF STEP 2
  • Support TLS routing on kubernetes
  • Support custom certificates for gateway and workspace endpoints · Issue #19394 · eclipse/che
  • Access to Kubernetes API when user is not a Kubernetes user Add an ability to use kubernetes API proxy on Kubernetes #19813 (we need to discuss if it can be added to the milestone scope)
  • Support CertManager in che operator for devworkspace controller deployment
  • Support deploying devworkspaces on Kubernetes
• Che-Theia should be able to use a plugin registry that is using an untrusted certificated ==> to be verify (it may already work because we are using internal links)
  • Dashboard should provision dashboard and plugin registry URLs into default DWT Dashboard should provision dashboard and plugin registry URLs into default DWT #19933
• Che-Theia should be able to download the project zip files even when the devfile registry use an untrusted certificate ==> OUT OF STEP 2: we don't support airgap
• WTO and Che with DevWorkspace Engine compatibility (@amisevsk gdoc proposal) OpenShift Console will support in 4.8, for CRW we need to discuss the compatibility with all-namespaces
  • Prototype DevWorkspace as dependency for WTO and CRW
• More fine grained startup details on dashboard
  • Propagate provisioning errors (components/workspaceRoutings)
• Dashboard (or other clients like chectl) should provide metadata about the origin of the devfile with DevWorkspace
• Workspaces authentication (postponed to milestone 3 when we will have Simplify authentication and authorization with a more flexible and lightweight approach #19182)
• Support for external dependencies repos (e.g. Nexus) that use an untrusted certificate
• Support for proxies that use an untrusted certificate
• Propagation of TLS certificates and other secrets:
  • How to handle configuration spread across DWO, WTO and DWCO
  • Add an ability to configure trust stores

[nickboldt]

Is this issue complete?

[l0rd]

I am closing this issue. The out of scope task are tracked by the following issues:

• Verify if downloading a vsix from a devfile registry with untrusted TLS cert work when DevWorkspace is enabled #20383 related to the recently found downstream bug [https://issues.redhat.com/browse/CRW-2200]
• Simplify authentication and authorization with a more flexible and lightweight approach #19182
• [devworkspace] add an ability to configure trust store e.g. for plugin registry with self-signed certs #17898
• [devworkspace] How to handle configuration spread across DWO, WTO and DWCO #19326
• Support OpenShift global proxy configuration and trusted certificate bundle when DevWorkspace is enabled #20386
• An admin should be able to specify CA certificates that need to be trusted on devfile v2 based workspaces #20387