Dashboard should inject controller.devfile.io/scc: container-build based on the CR property

[ibuziuk]

Is your task related to a problem? Please describe

As part of this issues, dashboard should inject the container build attribute based on the:

attributes:
  controller.devfile.io/scc: container-build

based on the CR property implemented as part of the #21752

Describe the solution you'd like

attribute is injected in every workspace is admin enabled the dedicated property

Describe alternatives you've considered

No response

Additional context

No response

[l0rd]

I have opened #21768 to makes the container build SCC configurable.

As a consequence Che dashboard should pick the SCC name from spec.devEnvironments.containerBuildConfiguration.openShiftSecurityContextConstraint (instead of using the hard-coded container-build SCC).

[l0rd]

I don't think this issue is necessary anymore. Setting containerOverrides should be enough. I am saying that because I have figure out that a Pod with the following spec (without the annotation openshift.io/scc: container-build but with the capabilities and allowPrivilegeEscalation: true) is automatically annotated by the scheduler:

apiVersion: v1
kind: Pod
metadata:
  name: rootless
spec:
  containers:
    - name: podman
      image: quay.io/mloriedo/podman:rootless
      imagePullPolicy: Always
      resources:
        limits:
          cpu: 100m
          memory: 1G
      securityContext:
        capabilities:
          add:
           - SETGID
           - SETUID
          drop:
           - KILL
           - MKNOD
        allowPrivilegeEscalation: true

[AObuchow]

This issue should be re-opened as it is still required, see #21770 (comment)

Edit: Never mind, I just saw that a PR was merged for this issue and that the issue has already been resolved.