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

• 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)