-
Notifications
You must be signed in to change notification settings - Fork 413
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Unable in trigger object to use a serviceaccount from an other namespace #1610
Comments
Issues go stale after 90d of inactivity. /lifecycle stale Send feedback to tektoncd/plumbing. |
/remove-lifecycle stale : no answer from assignee |
Hi @tizard34 can you provide me the full yaml for EL
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:<CURRENT_NAMESPACE>:" 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}'
The text was updated successfully, but these errors were encountered: