Skip to content

Commit 3428df1

Browse files
jsell-rhclaude
andcommitted
fix(e2e): always restart CP for fresh gRPC watch streams
kubectl set env is a no-op when values are unchanged, so the CP isn't restarted and its gRPC watch streams stay dead from a previous session. Add explicit rollout restart to ensure fresh watch connections on every test run. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
1 parent 4d9010a commit 3428df1

1 file changed

Lines changed: 4 additions & 1 deletion

File tree

components/ambient-api-server/test/e2e/rbac_e2e_test.sh

Lines changed: 4 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -372,7 +372,10 @@ kubectl set env deployment/ambient-control-plane -n "$NS" \
372372
OIDC_CLIENT_ID="$OIDC_CLIENT_ID_CP" \
373373
OIDC_CLIENT_SECRET="$OIDC_CLIENT_SECRET_CP" \
374374
OIDC_TOKEN_URL="$KC_TOKEN_URL"
375-
echo " Patched control plane with OIDC credentials"
375+
# Always restart CP to get fresh gRPC watch streams (set env is a no-op
376+
# if values unchanged, which means no rollout and stale streams persist)
377+
kubectl rollout restart deployment/ambient-control-plane -n "$NS" 2>/dev/null || true
378+
echo " Patched and restarted control plane"
376379
echo " Waiting for control plane rollout..."
377380
if ! kubectl rollout status deployment/ambient-control-plane -n "$NS" --timeout=120s; then
378381
echo "FATAL: Control plane rollout failed"

0 commit comments

Comments
 (0)