-
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
local role becomes cluster role when operator is deployed. #874
Comments
If you are creating a Is it causing issues for your operator's deployment? |
this is the OperatorGroup in the namespace where the operator is deployed:
is this global?
to answer your question, this is not affecting the deployment of the operator, however it is giving the operator much more permissions that is actually needs. |
@raffaelespazzoli Your CSV is using the Closing since I believe this will solve your problem. Please re-open if you have more questions! |
Enhancement Proposal to toggle this ability: |
I have an operator defined by the attached CSV
cert-utils-operator.zip
The thing to notice is that this operator has both a role and a cluster role.
when I make it available through the operator hub the attached install plan is created. At this point I still can see that there are two roles, one is local and on is a cluster role.
when the operator is deployed three roles are created:
this shoudl clarify what I mean:
Also the corresponding bindings to the operator service accounts are created.
This should not happen. However I am not sure if I am doing something wrong or if this is a bug.
The text was updated successfully, but these errors were encountered: