Mario Loriedo

@vaidotasp I think it makes sense to re-open this issue so that we can track what's supported and what's not. I am not sure why I closed it but we...

/remove-lifecycle stale

+1 to `autoProvision: false`. I have updated the description.

@MeghanaSrinath we (Che maintainers) are a small team with limited resources and we do not have access to GKE/AKS/EKS clusters so all our tests happen on Red Hat OpenShift clusters...

Ok @tolusha let's do that (git services are not required by default) but then we don't need the `disabled: ` field anymore.

With your proposal, if the admin wants to configure both gitlab.com and gitlab on prem can he do something like this: ```yaml spec: gitServices: gitlab: endpoint: gitlab.mycompany.com secret: gitlabinternal-oauth-config gitlab:...

Ok. Yes we need to consider that use case as well so it's better to use lists.

@brootware @edeandrea we understand the value of this feature. But allowing arbitrary developers to run a pod with ``` securityContext: privileged: true ``` as in the Tekton example will fail...

@edeandrea not when we tested ~1 year ago. But it looks like things have changed and we need to have a look again (c.f. this [issue](https://github.com/openshift/enhancements/issues/362) and related [OpenShift enhancement...

With [this merged](https://github.com/eclipse/che/issues/20459) and with the switch to DevWorkspace, it should be possible to `docker build` (buildah and docker should be part of [universal developer image](https://quay.io/repository/devfile/universal-developer-image)) from within a Che...