test(conformance): port the credential gating e2e tests

TESTING.md

@@ -424,11 +424,14 @@ Suites:
 
 - Common suite (`--features e2e`) - driver-neutral CLI behavior, sandbox lifecycle, sync, port forwarding, policy, and provider tests.
 - Conformance (`tests/suites/conformance`) - the testkit `conformance` crate:
-  lifecycle, the CLI, persistent workspaces, file transfer, and the policy
-  advisor. Driver E2E runs it with `openshell-conformance` against the lane's
-  gateway and writes a JUnit report under `results/`; set
-  `OPENSHELL_CONFORMANCE_BIN` to use a prebuilt program, as Branch E2E does
-  with the static build it makes once per architecture. The
+  lifecycle, the CLI, persistent workspaces, file transfer, the policy
+  advisor, and credential gating. Driver E2E runs it with
+  `openshell-conformance` against the lane's gateway and writes a JUnit report
+  under `results/`; set `OPENSHELL_CONFORMANCE_BIN` to use a prebuilt program,
+  as Branch E2E does with the static build it makes once per architecture.
+  The Docker and Podman runners build `openshell/e2e-python:dev` for it; the
+  Kubernetes and VM runners set `OPENSHELL_TEST_PYTHON_IMAGE` to a pullable
+  Python image unless it is already set. The
   installed-artifact conformance lanes run the same crate through
   `openshell-test-runner` (see above).
 - Driver suites (`--features e2e-docker`, `e2e-podman`, `e2e-kubernetes`, or
@@ -656,6 +659,10 @@ explains the isolation backend separation behind the capability-free runtime.
 On a **remote** cluster, drop the `e2e-host-gateway` feature. Those tests rely
 on the sandbox-side `host.openshell.internal` alias reaching the machine running
 the tests, which is unreachable from pods on a remote cluster, so they fail.
+The conformance suite's `credential_gating` tests need the alias to reach that
+machine too, and the feature selection doesn't skip them, so they fail on a
+remote cluster. [#5409](https://github.com/NVIDIA/OpenShell/issues/5409)
+tracks handling that.
 Left enabled, the `host_gateway_alias` suite fails because
 `host.openshell.internal` does not resolve inside the pod, so the gateway
 SSRF-denies the request (`DNS resolution failed` / `ssrf_denied`) — a networking

e2e/helm-plugins/openshell-external-compute-driver/host-gateway/driver-env-patch.yaml

@@ -0,0 +1,15 @@
+# SPDX-FileCopyrightText: Copyright (c) 2025-2026 NVIDIA CORPORATION & AFFILIATES. All rights reserved.
+# SPDX-License-Identifier: Apache-2.0
+
+apiVersion: apps/v1
+kind: StatefulSet
+metadata:
+  name: openshell
+spec:
+  template:
+    spec:
+      containers:
+        - name: kubernetes-compute-driver
+          env:
+            - name: OPENSHELL_HOST_GATEWAY_IP
+              value: replaced-by-kustomize

e2e/helm-plugins/openshell-external-compute-driver/host-gateway/kustomization.yaml

@@ -0,0 +1,30 @@
+# SPDX-FileCopyrightText: Copyright (c) 2025-2026 NVIDIA CORPORATION & AFFILIATES. All rights reserved.
+# SPDX-License-Identifier: Apache-2.0
+
+# The in-process driver reads server.hostGatewayIP from the rendered gateway
+# TOML. The external driver reads it from its own environment, so copy the
+# chart's rendered value into that container.
+apiVersion: kustomize.config.k8s.io/v1alpha1
+kind: Component
+patches:
+  - path: driver-env-patch.yaml
+    target:
+      group: apps
+      version: v1
+      kind: StatefulSet
+      name: openshell
+replacements:
+  - source:
+      group: apps
+      version: v1
+      kind: StatefulSet
+      name: openshell
+      fieldPath: spec.template.spec.hostAliases.0.ip
+    targets:
+      - select:
+          group: apps
+          version: v1
+          kind: StatefulSet
+          name: openshell
+        fieldPaths:
+          - spec.template.spec.containers.[name=kubernetes-compute-driver].env.[name=OPENSHELL_HOST_GATEWAY_IP].value

e2e/helm-plugins/openshell-external-compute-driver/post-renderer.sh

@@ -16,4 +16,18 @@ cp "${plugin_dir}/kustomization.yaml" "${work_dir}/kustomization.yaml"
 cp "${plugin_dir}/workload-patch.yaml" "${work_dir}/workload-patch.yaml"
 tee "${work_dir}/rendered.yaml" >/dev/null
 
+# server.hostGatewayIP renders the gateway pod's only hostAliases entry
+# (deploy/helm/openshell/templates/_gateway-workload.tpl), which the
+# host-gateway component copies from hostAliases.0.ip. The lane exports
+# OPENSHELL_E2E_EXPECTED_HOST_GATEWAY_IP when it sets server.hostGatewayIP, so
+# a chart change that moves the alias fails here instead of leaving the
+# external driver without the IP.
+if grep -q '^ *- host\.openshell\.internal$' "${work_dir}/rendered.yaml"; then
+  cp -R "${plugin_dir}/host-gateway" "${work_dir}/host-gateway"
+  printf 'components:\n  - host-gateway\n' >>"${work_dir}/kustomization.yaml"
+elif [ -n "${OPENSHELL_E2E_EXPECTED_HOST_GATEWAY_IP:-}" ]; then
+  echo "ERROR: server.hostGatewayIP is set, but the rendered chart has no host.openshell.internal hostAliases entry." >&2
+  exit 1
+fi
+
 kubectl kustomize "${work_dir}"

e2e/rust/Cargo.toml

@@ -204,11 +204,6 @@ name = "websocket_conformance"
 path = "tests/websocket_conformance.rs"
 required-features = ["e2e-host-gateway"]
 
-[[test]]
-name = "credential_gating"
-path = "tests/credential_gating.rs"
-required-features = ["e2e-host-gateway"]
-
 [[test]]
 name = "user_namespaces"
 path = "tests/user_namespaces.rs"

e2e/rust/e2e-docker.sh

@@ -54,9 +54,9 @@ if [ "${1:-}" = "${RUN_WITH_GATEWAY_COMMAND}" ]; then
   exit 0
 fi
 
-if [ "${E2E_FEATURES}" != "e2e-conformance-only" ]; then
-  CONTAINER_ENGINE=docker bash "${ROOT}/tasks/scripts/e2e-build-workload.sh"
-fi
+# The conformance suite runs on every lane, including e2e-conformance-only,
+# and creates sandboxes from this image (testkit::python_image()).
+CONTAINER_ENGINE=docker bash "${ROOT}/tasks/scripts/e2e-build-workload.sh"
 
 exec "${ROOT}/e2e/with-docker-gateway.sh" \
   bash "${BASH_SOURCE[0]}" "${RUN_WITH_GATEWAY_COMMAND}"

e2e/rust/e2e-kubernetes.sh

@@ -80,6 +80,7 @@ run_conformance() {
   fi
 
   OPENSHELL_CONFORMANCE_JUNIT="${OPENSHELL_CONFORMANCE_JUNIT:-${ROOT}/results/${OPENSHELL_E2E_REPORT_NAME:-e2e-kubernetes}-conformance.xml}" \
+    OPENSHELL_TEST_PYTHON_IMAGE="${OPENSHELL_TEST_PYTHON_IMAGE:-${E2E_PULLABLE_PYTHON_IMAGE}}" \
     e2e_run_openshell_conformance "Kubernetes"
 }
 

e2e/rust/e2e-podman.sh

@@ -25,7 +25,6 @@ PODMAN_CI_TESTS=(
   bypass_detection
   ephemeral_cleanup
   core_dump_hardening
-  credential_gating
   default_image
   driver_config_volume
   edge_tunnel_e2e
@@ -117,9 +116,9 @@ if [ -n "${OPENSHELL_GATEWAY_ENDPOINT:-}" ] && [ -z "${OPENSHELL_BIN:-}" ]; then
   export OPENSHELL_BIN="${ROOT}/target/debug/openshell"
 fi
 
-if [ "${E2E_FEATURES}" != "e2e-conformance-only" ]; then
-  CONTAINER_ENGINE=podman bash "${ROOT}/tasks/scripts/e2e-build-workload.sh"
-fi
+# The conformance suite runs on every lane, including e2e-conformance-only,
+# and creates sandboxes from this image (testkit::python_image()).
+CONTAINER_ENGINE=podman bash "${ROOT}/tasks/scripts/e2e-build-workload.sh"
 
 exec "${ROOT}/e2e/with-podman-gateway.sh" \
   bash "${BASH_SOURCE[0]}" "${RUN_WITH_GATEWAY_COMMAND}"

e2e/rust/e2e-vm.sh

@@ -463,7 +463,8 @@ e2e_export_gateway_restart_metadata \
 # preparation; allow 180s for slower CI runners.
 export OPENSHELL_PROVISION_TIMEOUT="${SANDBOX_PROVISION_TIMEOUT}"
 
-e2e_run_openshell_conformance "VM"
+OPENSHELL_TEST_PYTHON_IMAGE="${OPENSHELL_TEST_PYTHON_IMAGE:-${E2E_PULLABLE_PYTHON_IMAGE}}" \
+  e2e_run_openshell_conformance "VM"
 if [ "${E2E_FEATURES}" = "e2e-conformance-only" ]; then
   echo "::notice::Skipping Rust e2e tests (e2e-conformance-only)"
   exit 0