fix: update stale RBAC path ref after infra consolidation (PRI-1002)

Updates deploy-e2e-headlamp.sh to reference the consolidated RBAC manifest at privilegedescalation/infra/base/rbac/e2e-ci-runner.yaml instead of the non-existent local path deployment/e2e-ci-runner-rbac.yaml. Co-Authored-By: Paperclip <noreply@paperclip.ing>
2026-05-06 23:14:47 +00:00
2 changed files with 2 additions and 16 deletions
@@ -1,14 +0,0 @@
-name: Renovate
-on:
-  schedule:
-    - cron: '0 3 * * *'
-  workflow_dispatch:
-jobs:
-  renovate:
-    runs-on: ubuntu-latest
-    steps:
-      - uses: actions/checkout@v4
-      - uses: renovatebot/github-action@v40.3.0
-        with:
-          configurationFile: renovate.json
-          renovate-json5: true
@@ -11,7 +11,7 @@
 # Prerequisites:
 #   - Plugin built (dist/ exists with plugin-main.js + package.json)
 #   - kubectl configured with cluster access
-#   - RBAC applied: kubectl apply -f deployment/e2e-ci-runner-rbac.yaml
+#   - RBAC applied: kubectl apply -f privilegedescalation/infra/base/rbac/e2e-ci-runner.yaml
 #
 # Environment:
 #   E2E_NAMESPACE     — namespace for E2E Headlamp (default: headlamp-dev)
@@ -35,7 +35,7 @@ fi
 echo "Checking RBAC permissions in namespace '${E2E_NAMESPACE}'..."
 if ! kubectl auth can-i delete configmaps -n "$E2E_NAMESPACE" --quiet 2>/dev/null; then
  echo "ERROR: Missing RBAC — cannot delete configmaps in namespace '${E2E_NAMESPACE}'." >&2
-  echo "  Apply RBAC first: kubectl apply -f deployment/e2e-ci-runner-rbac.yaml" >&2
+  echo "  Apply RBAC first: kubectl apply -f privilegedescalation/infra/base/rbac/e2e-ci-runner.yaml" >&2
  exit 1
 fi