-
Notifications
You must be signed in to change notification settings - Fork 23
missing permission in role yaml #95
Comments
volumereplicationclass rules are defined in different files (these are auto-generated files) and this is expected and you need to apply cluster roles for volumereplicationclass. cc @sp98 |
@Madhu-1 the issue is that the required rules for the replication operator are defined in different files, instead of one (as in other csi sidecars, e.g. provisioner, attacher, etc...). and the yaml with the required replication class rule has a comment that says the rule is for end users, which is misleading, since it implies that the rule is not meant for the replication operator |
@oriyarde the volume replication is generated from the operator scale folding but the other CSI sidecars are not. that is the reason for having it in different files.
AFAIK the comment is adding by the operator sdk. lets hear from @raghavendra-talur @sp98 on that |
@Madhu-1 could all the required rules at least be generated into a single directory? |
Sure we can document the deployment and RBAC in a readme at least of this one. |
Hi,
I tried to deploy the replication operator as a sidecar container inside our csi controller pod.
I have a cluster role binding with a service account ("ibm-block-csi-controller-sa") and with a cluster role for the replication operator.
I copied said cluster role rules from the role yaml rules, and the replication operator log started nicely:
but then entered an error loop:
after adding the following rule (copied from the volumereplicationclass viewer role yaml, which is "for end users"):
the error was gone.
so I think this rule is missing in the role yaml.
The text was updated successfully, but these errors were encountered: