-
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
Packages ClusterRoles with Triggers deployment for eventlistener #1158
Conversation
/cc @dibyom |
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.
Looks good...my only comment is to see if we can make the names a bit smaller but that's minor
config/200-clusterrole.yaml
Outdated
apiVersion: rbac.authorization.k8s.io/v1 | ||
kind: ClusterRole | ||
metadata: | ||
name: tekton-triggers-eventlistener |
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.
what do you think of calling this simply eventlistener-roles
and the other one eventlistener-clusterroles
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.
end users might have many things installed on the cluster so if we keep tekton-triggers-
as prefix so wouldn't it be easier to understand where the clusterrole came from.
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.
and also it would be uniform with other resources we package
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.
fair enough!
/lgtm |
/approve |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: dibyom 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 |
/hold |
let me rename it to |
This packages 2 clusterroles with triggers deployment for el that can be used by users for their deployments. User will have to creates following resources: - a serviceaccount which would be used with eventlistener - a rolebinding with above sa and `tekton-triggers-eventlistener-roles` clusterrole - a clusterrolebinding with above sa and `tekton-triggers-eventlistener-clusterroles` clusterrole Signed-off-by: Shivam Mukhade smukhade@redhat.com
Signed-off-by: Shivam Mukhade smukhade@redhat.com
/hold cancel |
/lgtm |
@sm43 One thing I forgot -- could you add a release notes section to this PR? /kind feature |
Yup! |
This packages 2 clusterroles with triggers deployment for el
that can be used by users for their deployments.
User will have to creates following resources:
tekton-triggers-eventlistener-roles
clusterroletekton-triggers-eventlistener-clusterroles
clusterrole
Closes #1119
Signed-off-by: Shivam Mukhade smukhade@redhat.com
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