-
Notifications
You must be signed in to change notification settings - Fork 116
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
Exclude RoleBinding from sample-strategies.yaml #1823
Exclude RoleBinding from sample-strategies.yaml #1823
Conversation
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
Signed-off-by: Sascha Schwarze <[email protected]>
6db4646
to
9fbb7a3
Compare
Rebased |
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.
/approve
/lgtm
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: qu1queee 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
For the multiarch buildstrategy, https://github.com/shipwright-io/build/tree/main/samples/v1beta1/buildstrategy/multiarch-native-buildah, we are delivering also a ClusterRole and RoleBindings so that the running build has the necessary permissions to manage Jobs and Pods in the cluster.
As described in https://github.com/shipwright-io/build/blob/main/docs/buildstrategies.md#installing-multi-arch-native-buildah-strategy, the RoleBinding must be installed in the namespace(s) where the build strategy will be used. As we cannot know which namespaces those are, we should not include this file in our sample-strategies.yaml.
This PR excludes it like we already also exclude our sample namespaces build strategies.
Submitter Checklist
Release Notes