Support Devfile v2 outer loop components of type `image` and `kubernetes`

[l0rd]

Is your enhancement related to a problem? Please describe

Che currently ignores these component types although they are used in registry.devfile.io samples.

👉 Note that this issue is only about the “outer loop” implementation of these components. Outer loop means that the components are created after a workspace start-up to test in a prod like deployment. There is a separate issue for inner loop support.

A component is considered “outer loop” if any of these conditions apply (c.f. https://github.com/devfile/library/pull/127/files):

• it’s associated to a command of type apply
• it’s a kubernetes or openshift and has deployByDefault: false (the version of the spec is 2.2 or higher)
• it’s an image (and do NOT have autoBuild: true) (the version of the spec is 2.2 or higher)

Describe the solution you'd like

Pre-process the Devfile to replace the outer loop component with an exec command:

• kubernetes or openshift components are replaced with a kubectl apply or oc apply command in the dev component
• image components are replaced with a command that does a build, in this case the command is configurable as there are multiple options like buildah, kaniko, docker build or oc start-build on OCP.

2 alternative approaches

The “outer loop” components replacement with exec commands can be a responsibility of the dashboard OR of the IDEs.

Plus if it’s done by the dashboard: it works for any IDE
Plus if it’s done by the IDEs: it works for scenarios without Che dashboard (i.e. k apply -f devworkspace.yaml)

[ibuziuk]

from the architectural point of view, I would like to avoid adding more complexity to the dashboard and making it the "glue" / pre-processing component without which some of the DevWorkspace flows would not work (like in this particular case with the apply:component: commands)

[che-bot]

Issues go stale after 180 days of inactivity. lifecycle/stale issues rot after an additional 7 days of inactivity and eventually close.

Mark the issue as fresh with /remove-lifecycle stale in a new comment.

If this issue is safe to close now please do so.

Moderators: Add lifecycle/frozen label to avoid stale mode.