Add support for devfile kubernetes and openshift components

[sleshchenko]

Is your enhancement related to a problem? Please describe.

Che currently ignores kubernetes and openshift components. These were previously supported by the che-server workspaces engine.

Describe the solution you'd like

• Do not re-implement a che-server like behavior (i.e. extract the container of a pod/deployment and add it to the workspace pod): in the new implementation, an inner loop kubernetes or openshift component, would be applied without any modification.
• This issue is not about the outer loop kubernetes and openshift components (there is a specific issue for that)
• Block privileges escalations scenarios (i.e. if the user doesn’t have the privileges to create a pod in a given namespace, this feature should not allow him to do it)

Release Notes Text

Eclipse Che now supports devfile components of type kubernetes and openshift. That allow to reference Kubernetes and OpenShift manifests in a devfile and include them as part of the workspace. Devfile components of type volume and container were already supported, components of type image are not supported yet.

[Bolodya1997]

Is there any plan for implementing this feature?

In out project we want to create k8s Secret component with automount credentials annotation to add git credentials from the private Git repositories other than the devfile location.

Example:

components:
  - name: git-credentials-gitlab
    kubernetes:
      inlined: |
        {
          "kind": "Secret",
          "apiVersion": "v1",
          "metadata": {
            "name": "git-credentials-gitlab",
            "annotations": {
              "controller.devfile.io/mount-path": "/home/theia/.git-credentials"
            },
            "labels": {
              "controller.devfile.io/git-credential": "true",
              "controller.devfile.io/watch-secret": "true"
            }
          },
          "type": "Opaque",
          "data": {
            "credentials": "aHR0cDovL...b2NhbA=="
          }
        }

[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.

[l0rd]

This has been addressed by devfile/devworkspace-operator#961

[devstudio-release]

sync'd to Red Hat JIRA https://issues.redhat.com/browse/CRW-3851