-
Notifications
You must be signed in to change notification settings - Fork 419
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
switch trigger sa based auth to impersonate; change secret ref to string and by extension same namespace as EventListener #705
switch trigger sa based auth to impersonate; change secret ref to string and by extension same namespace as EventListener #705
Conversation
The following is the coverage report on the affected files.
|
ff655ae
to
16fa689
Compare
The following is the coverage report on the affected files.
|
16fa689
to
da10d43
Compare
The following is the coverage report on the affected files.
|
da10d43
to
c895aff
Compare
The following is the coverage report on the affected files.
|
c895aff
to
d5851cc
Compare
The following is the coverage report on the affected files.
|
d5851cc
to
859472a
Compare
The following is the coverage report on the affected files.
|
19f19e0
to
66f42f1
Compare
The following is the coverage report on the affected files.
|
Thanks @gabemontero I think this should address #679 too? |
yes it does @dibyom |
forgot to /hold cancel |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
/lgtm
I think we should move to ServiceAccountName
string instead of taking it as ServiceAccount
LocalObjectReference. Maybe a pr later on which deprecate ServiceAccount
in favour of ServiceAccountName
.
Then, this will have the same format as we do in other Tekton resources which requires ServiceAccount.
I'm fine with switching to thanks |
3835cfc
to
2ba7ea1
Compare
2ba7ea1
to
690cfe6
Compare
The following is the coverage report on the affected files.
|
The following is the coverage report on the affected files.
|
oh and I removed more unneeded code from auth_override.go, hence the delta change we are now down to one method which we have to use the "fake" version of in the unit tests to bypass actual client access to a cluster the function is covered by the e2e that validates trigger level SA |
690cfe6
to
5e53cc7
Compare
The following is the coverage report on the affected files.
|
5e53cc7
to
2ce2246
Compare
The following is the coverage report on the affected files.
|
2ce2246
to
d774140
Compare
The following is the coverage report on the affected files.
|
…mespace as EventListener
d774140
to
f6264b9
Compare
The following is the coverage report on the affected files.
|
/approve |
Thanks for the clarification! |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
/lgtm
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: dibyom, khrm The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
Changes
As the efforts to progress support for multi-tenant event listeners has evolved, most notably around the notion of breaking out
EventListenerTrigger
into a Trigger CRD, or an analogous resource like a PipelineRecipe defined in the pipelines project, some evolution of the finer grained auth originally introduced in #454 seemed appropriate.This PR currently has 2 commits with that goal in mind:
ObjectReference
to aLocalObjectReference
, hence scoping the SA's available for use to the SA's present in the namespace of the trigger object itself; we originally scoped it asObjectReference
because the interceptors had a a multi-namespace scope for secrets per https://github.com/tektoncd/triggers/blob/master/pkg/apis/triggers/v1alpha1/event_listener_types.go#L97-L104 however as the various TEPs/proposals have evolved that no longer seems like a valid motivator for having this SA reference be multi namespaceAnd as a result this
Fixes #679
Submitter Checklist
These are the criteria that every PR should meet, please check them off as you
review them:
See the contribution guide for more details.
Release Notes