-
Feature
-
Resolution: Done
-
Major
-
None
-
False
-
None
-
False
To run podman build from a Dev Spaces workspace a user can specify an attribute controller.devfile.io/scc: container-build in a devfile. This mechanism has a few drawbacks:
PRODUCTIZATION ISSUE:
It works only upstream: downstream UDI images don't include ROOTLESS buildah or podman (only the RPMs are installed) RESOLVED
DEVWORKSPACE ISSUE:
We have observed that in some customers clusters the SCC specified in the attributes is ignored subtask:
OPERATOR + DASHBOARD ISSUE:
Add some CheCluster fields to configure and enable the container build capabilties subtasks:
- Allow che administrators to enable container build capabilities for developers workspaces RESOLVED
- Automatically create the container build SCC if containerBuildCapability is enabled RESOLVED
- Automatically add the container build SCC to users if containerBuildCapability is enabled RESOLVED
- Dashboard should inject controller.devfile.io/scc: container-build based on the CR property - RESOLVED
- Update the way the workspace SA is granted the privileges to use an SCC (using role/rolbindings) - RESOLVED
- Specify the workspace Pods securityContext (SETGID and SETUID) when developers have container build capabilities - RESOLVED, 3.5 (7.59)
- is related to
-
-
- Closed
-
-
CRW-3358 udi: odo :: install odo 2.5.1 via rpm (not curl or fetch-artifacts); do not update to 3.0.0.RC1
-
- Closed
-
-
CRW-3344 [RN] Update VSCode OpenShift Connector plugin to latest OpenShift Toolkit 1.0 to support odo 3.0
-
- Closed
-
- relates to
-
-
- Resolved
-
- links to
