Support devfile with more than one Kubernetes tool

[l0rd]

Description

Devfile example:

specVersion: 0.0.1
name: fix-the-kube
projects:
  - name: nodejs-mongo-app
    source:
      type: git
      location: 'https://github.com/ijason/NodeJS-Sample-App.git'
tools:
  - name: theia-editor
    type: cheEditor
    id: org.eclipse.che.editor.theia:1.0.0
  - name: exec-plugin
    type: chePlugin
    id: che-machine-exec-plugin:0.0.1
  - name: mongodb
    type: kubernetes
    local: mongo-controller.yaml
  - name: nodejs
    type: kubernetes
    local: node-controller.yaml

Controllers yamls can be found at kubernetes example

[sleshchenko]

It's expected behavior for the time being. But it would be a great enhancement to support multiple kubernetes/openshift/dockerimage tools.

[garagatyi]

@l0rd Now we translate k8s/OS/dockerimage tool into the recipe of the workspace created by the devfile. Do you want us to create algorithm for merging several tools into a single recipe?

[l0rd]

@garagatyi yeah...I mean I don't know if making it possible to have more than one recipe is simpler. But anyway the algorithm should be extracting the container part of every "tool" and merging it in the workspace deployment (where we merge plugins and editors containers as well).

[garagatyi]

@l0rd I assume that we don't need to implement support of conversion of workspace config back to several k8s tools, right? In fact we don't support conversion workspace config based on k8s recipe back to devfile at all. Implementation of this for several k8s tools would be complicated and would require more time.

[l0rd]

@garagatyi correct. I think that rather than supporting ws.config => devfile conversion we should get rid of ws.config at all. But that will come later.

[garagatyi]

@l0rd 👍 this is what we keep coming across with Serhii and Lukas :)

[garagatyi]

Since OSIO-Che and Che platform teams are not yet sure who will work on this issue we discussed technical details of the implementation with @sleshchenko
We decided that scope of this task would be:

• devfile code should add tools content into recipe of type kubernetes list
• devfile code should convert dockerimage tool to k8s deployment or pod and also add it to the kubernetes list
• workspace start code should merge all the deployments/pods/os templates from this kubernetes list into a single deployment (since we don't support multiple deployments yet)
• won't implement export (was just confirmed by Mario)
• but add tool meta info into k8s objects to be able to implement export of them to devfile tools later (if needed)

[skabashnyuk]

@garagatyi @ibuziuk we are taking this issue to our sprint. @sleshchenko are going to work on it.