-
Notifications
You must be signed in to change notification settings - Fork 544
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
Allow resolving ClusterRoles #477
Allow resolving ClusterRoles #477
Conversation
install into olm namespace instead of kube-system
this is parallel to the permissions block, but describes clusterroles and clusterrolebindings the specific placement matches the existing permissions block, which will likely change in the next apiversion
installplan resolution
also refactored some of the InferGVK code to be re-usable in step resolution
/approve |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: ecordell 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 |
@@ -235,7 +234,7 @@ func resolveCRDDescription(sourceRefs []registry.SourceRef, existingCRDOwners ma | |||
func resolveRBACStepResources(csv *v1alpha1.ClusterServiceVersion) ([]v1alpha1.StepResource, error) { | |||
var rbacSteps []v1alpha1.StepResource | |||
|
|||
// User a StrategyResolver to | |||
// User a StrategyResolver to get the strategy details |
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 |
Allow resolving ClusterRoles
clusterPermissions
to CSV install strategy (just for v1alpha1, we'll revisit for next api version)This greatly expands the power of operators that can be installed with OLM. Restricting what operators can do can be achieved be reducing the scope of permissions given to OLM.
Fixes #477