fix(network): narrow additional CA review scope

Signed-off-by: Jesse Jaggars <jjaggars@redhat.com>

Author: jhjaggars

deploy/helm/openshell/README.md.gotmpl

@@ -231,8 +231,13 @@ The driver manages the deterministic name
 `server.sandboxJwt.gatewayId`, or the chart fullname when unset). Its `get` and
 `patch` permissions must be restricted to that exact name; `create` must remain
 a separate unrestricted ConfigMap permission because Kubernetes cannot apply
-`resourceNames` to create authorization. If you render the TOML setting outside
-this Helm value, grant that same split RBAC policy in every sandbox namespace.
+`resourceNames` to create authorization. Enabling this therefore gives the
+gateway/driver service account namespace-wide ConfigMap-create authority. In
+managed/operator modes, the chart's ClusterRoleBinding makes that permission
+cluster-wide for the bound service account; use a dedicated service account and
+scoped bindings when that boundary matters. If you render the TOML setting
+outside this Helm value, grant that same split RBAC policy in every sandbox
+namespace.
 
 Disabling the setting intentionally does not delete driver-managed ConfigMaps:
 the driver has no list/delete permissions, and a shared or operator namespace

deploy/helm/openshell/templates/clusterrole.yaml

@@ -95,7 +95,10 @@ rules:
   # The Kubernetes driver reads and server-side-applies only its deterministic,
   # gateway-scoped destination CA ConfigMap in selected namespaces. CREATE
   # cannot use resourceNames because Kubernetes authorizes it before the name
-  # is available.
+  # is available. This is a namespace-wide ConfigMap-create capability when
+  # bound through a Role, and becomes cluster-wide when this ClusterRole is
+  # bound cluster-wide; use a dedicated service account and scoped bindings
+  # when that boundary matters.
   - apiGroups:
       - ""
     resources:

skills/debug-openshell-cluster/SKILL.md

@@ -431,7 +431,11 @@ chart fullname when it is unset. The managed ConfigMap must have
 `openshell.ai/managed-by=openshell` and the matching
 `openshell.ai/gateway-id` label. The chart grants `get`/`patch` only on this
 exact name and separate unrestricted `create` (Kubernetes cannot restrict a
-create with `resourceNames`). Check both the object and authorization:
+create with `resourceNames`). Enabling this gives the gateway/driver service
+account namespace-wide ConfigMap-create authority. In managed/operator modes,
+the chart's ClusterRoleBinding makes that permission cluster-wide for the bound
+service account; prefer a dedicated service account and scoped bindings when
+that boundary matters. Check both the object and authorization:
 
 ```bash
 kubectl -n <sandbox-namespace> get configmap \