Root cause:kubectl get nodes requires cluster-scope RBAC that ci-tekton-trigger SA lacks.
Fixes:
Replace kubectl get nodes with kubectl get namespaces (namespace-scoped, allowed)
Guard canary cleanup: skip kubectl delete when POD_NAME is empty (prevents resource name may not be empty)
Fixes CI run #1023 (job 1350).
**Root cause:** `kubectl get nodes` requires cluster-scope RBAC that `ci-tekton-trigger` SA lacks.
**Fixes:**
1. Replace `kubectl get nodes` with `kubectl get namespaces` (namespace-scoped, allowed)
2. Guard canary cleanup: skip `kubectl delete` when `POD_NAME` is empty (prevents `resource name may not be empty`)
- Replace 'kubectl get nodes' (cluster-scope, forbidden for ci-tekton-trigger SA)
with 'kubectl get namespaces' (namespace-scoped, allowed)
- Guard canary cleanup against empty POD_NAME to prevent 'resource name may not be empty'
Fixes CI run #1023
rock
merged commit 63ec2ddf68 into main2026-09-26 11:05:18 +00:00
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Fixes CI run #1023 (job 1350).
Root cause:
kubectl get nodesrequires cluster-scope RBAC thatci-tekton-triggerSA lacks.Fixes:
kubectl get nodeswithkubectl get namespaces(namespace-scoped, allowed)kubectl deletewhenPOD_NAMEis empty (preventsresource name may not be empty)