From 832ccf52a1321bea284e6949f8a2b3732ecf8bec Mon Sep 17 00:00:00 2001 From: John Coffey Date: Wed, 18 Nov 2026 18:03:21 -0700 Subject: [PATCH] Enforce Pod Security restricted on the inbuxa namespace The chart's pods must pass restricted (K-C4); the lab now refuses any that don't, and warns when a template wouldn't. --- lab/up.sh | 3 +++ 1 file changed, 3 insertions(+) diff --git a/lab/up.sh b/lab/up.sh index 2cbc369..69d5d23 100755 --- a/lab/up.sh +++ b/lab/up.sh @@ -14,6 +14,9 @@ step "kind cluster" kind get clusters 2>/dev/null | grep -qx "$KIND_CLUSTER" || kind create cluster --name "$KIND_CLUSTER" --config "$here/kind.yaml" --wait 120s kubectl config use-context "kind-$KIND_CLUSTER" >/dev/null for ns in data inbuxa; do kubectl create namespace "$ns" --dry-run=client -o yaml | kubectl apply -f - >/dev/null; done +# inbuxa's pods run under Pod Security "restricted", enforced (K-C4) +kubectl label --overwrite namespace inbuxa \ + pod-security.kubernetes.io/enforce=restricted pod-security.kubernetes.io/warn=restricted >/dev/null step "CloudNativePG operator" helm upgrade --install cnpg cnpg/cloudnative-pg --version "$CNPG_CHART" -n cnpg-system --create-namespace --wait >/dev/null -- 2.54.0