Chris Farhood 3c6d77eb49 fix(e2e): apply RBAC in workflow before pre-flight check ...

The E2E workflow now applies both RBAC manifests (e2e-ci-runner-rbac.yaml
and polaris-rbac.yaml) in the same step, then verifies permissions with a
two-namespace pre-flight check. This makes the workflow self-sufficient — no
manual RBAC application or cluster-prep step required before CI runs.

Changes:
- Workflow now applies e2e-ci-runner-rbac.yaml + polaris-rbac.yaml before
  the pre-flight check (previously only applied polaris-rbac.yaml and only
  checked, not applied, e2e-ci-runner-rbac.yaml)
- Pre-flight check verifies can-i delete configmaps in privilegedescalation-dev
  AND can-i get services/proxy in polaris before proceeding
- e2e-ci-runner-rbac.yaml now includes Role + RoleBinding for the polaris
  namespace so the CI runner can apply the dashboard proxy RBAC

Fixes PRI-264 / PRI-324.

Co-Authored-By: Paperclip <noreply@paperclip.ing>

2026-05-03 18:24:21 +00:00

..

ci.yaml

Merge PR #20

2026-03-08 11:16:32 +00:00

dual-approval.yaml

fix: pass pr_number to dual-approval-check workflow (#119)

2026-04-15 03:33:19 +00:00

e2e.yaml

fix(e2e): apply RBAC in workflow before pre-flight check

2026-05-03 18:24:21 +00:00

release.yaml

ci: pass GitHub App token secrets to release workflow (#76)

2026-03-20 13:24:35 +00:00