Open tizard34 opened 1 year ago
Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale
with a justification.
Stale issues rot after an additional 30d of inactivity and eventually close.
If this issue is safe to close now please do so with /close
with a justification.
If this issue should be exempted, mark the issue as frozen with /lifecycle frozen
with a justification.
/lifecycle stale
Send feedback to tektoncd/plumbing.
/remove-lifecycle stale : no answer from assignee
Hi @tizard34 Apologize for the late reply
can you provide me the full yaml for EL
apiVersion: triggers.tekton.dev/v1alpha1
kind: EventListener
metadata:
name: my-eventlistener
namespace: app-pipelines-namespace
spec:
namespaceSelector: {}
resources: {}
serviceAccountName: default
triggers:
- bindings: ....
interceptors: ...
name: trigger-build
serviceAccountName: 'system:serviceaccount:other-namespace:default'
template: ....
I mean bindings and interceptor details etc....
so that i can try to reproduce the issue
Expected Behavior
Specify a serviceaccount from an other namespace must be allowed in trigger object
Actual Behavior
If the serviceaccount used in the EventListener has not the right to impersonate. The EventListener Pod write this logs :
If the serviceaccount used in the EventListener has the right to impersonate. The EventListener Pod write this logs :
It seems that the prefix "system:serviceaccount::" is always added to the trigger serviceaccount name.
Steps to Reproduce the Problem
Additional Info
Kubernetes version:
Output of
kubectl version
:Tekton Pipeline version:
Output of
tkn version
orkubectl get pods -n tekton-pipelines -l app=tekton-pipelines-controller -o=jsonpath='{.items[0].metadata.labels.version}'