You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Commit 8d70aa8
Browse filesBrowse the repository at this point in the historyBrowse files
docs(helm): make OpenShift SCC guidance topology-aware in chart README
The chart README's OpenShift quick-start told every user to grant the
privileged SCC to the sandbox service account. For the proxy-pod topology
that is both unnecessary and counter to the topology's purpose: network
enforcement runs outside the pod, so sandbox pods are non-root with drop-ALL
and admit under the built-in nonroot-v2 SCC.
Split the guidance by topology: combined/sidecar keep the privileged grant;
proxy-pod skips it and binds nonroot-v2 via
sandboxServiceAccount.openshift.nonrootSCC=true (no manual oc adm policy
step). Edit the README.md.gotmpl source and regenerate README.md. The
published docs page already carries the topology-aware guidance.
Reported in review by 2000krysztof.
Signed-off-by: Russell Bryant <[email protected]>
See the full [OpenShift install guide](https://docs.nvidia.com/openshell/latest/kubernetes/openshift) for details. Quick start:
35
+
See the full [OpenShift install guide](https://docs.nvidia.com/openshell/latest/kubernetes/openshift) for details. The SCC the sandbox service account needs depends on the supervisor topology.
36
+
37
+
### combined (default) or sidecar
38
+
39
+
These topologies enforce network policy inside the sandbox pod and require the `privileged` SCC on the sandbox service account:
36
40
37
41
```shell
38
42
# Precreate the openshell namespace so we can create the SCC cluster role
39
43
oc create ns openshell
40
44
41
-
# Sandboxes are deployed into the openshell namespace and use the openshell-sandbox service account
45
+
# Sandboxes use the openshell-sandbox service account
Network enforcement moves to a separate supervisor pod, so sandbox pods run non-root with `drop: ALL` and need no elevated privileges. The built-in `nonroot-v2` SCC is sufficient — do not grant `privileged`. Let the chart bind `nonroot-v2` via `sandboxServiceAccount.openshift.nonrootSCC=true` (requires the default `workspaceMode=shared`); no manual `oc adm policy` step for the sandbox service account is needed:
See the full [OpenShift install guide](https://docs.nvidia.com/openshell/latest/kubernetes/openshift) for details. Quick start:
35
+
See the full [OpenShift install guide](https://docs.nvidia.com/openshell/latest/kubernetes/openshift) for details. The SCC the sandbox service account needs depends on the supervisor topology.
36
+
37
+
### combined (default) or sidecar
38
+
39
+
These topologies enforce network policy inside the sandbox pod and require the `privileged` SCC on the sandbox service account:
36
40
37
41
```shell
38
42
# Precreate the openshell namespace so we can create the SCC cluster role
39
43
oc create ns openshell
40
44
41
-
# Sandboxes are deployed into the openshell namespace and use the openshell-sandbox service account
45
+
# Sandboxes use the openshell-sandbox service account
Network enforcement moves to a separate supervisor pod, so sandbox pods run non-root with`drop: ALL`and need no elevated privileges. The built-in `nonroot-v2` SCC is sufficient — do not grant `privileged`. Let the chart bind `nonroot-v2` via `sandboxServiceAccount.openshift.nonrootSCC=true` (requires the default `workspaceMode=shared`); no manual `oc adm policy` step for the sandbox service account is needed:
0 commit comments