Add Role For Monitoring Release Pipelines #5818
Conversation
|
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: rhartman93 The full list of commands accepted by this bot can be found here.
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
|
Hi @rhartman93. Thanks for your PR. I'm waiting for a redhat-appstudio member to verify that this patch is reasonable to test. If it is, they should reply with Once the patch is verified, the new status will be reflected by the I understand the commands that are listed here. Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. |
| apiVersion: rbac.authorization.k8s.io/v1 | ||
| kind: ClusterRole | ||
| metadata: | ||
| name: monitor-release-pipeline-role |
There was a problem hiding this comment.
this can be used for any type of pipeline though
There was a problem hiding this comment.
Are you saying I should rename it to be more generic? or suggesting that there's a way I could make the role more tailored to release pipelines?
| name: monitor-release-pipeline-role | ||
| rules: | ||
| - apiGroups: | ||
| - tekton.dev |
There was a problem hiding this comment.
you may have to separate the tekton and the core ones?
Co-authored-by: Deepak Chourasia <[email protected]>
Co-authored-by: Deepak Chourasia <[email protected]>
|
| We want to create a service account that can be used by users to automate monitoring the status of their managed |
We want to create a service account that can be used by users to automate monitoring the status of their managed release pipelines. The thought for now is it will only require:
permissions for: