Skip to content

Conversation

@ayushsatyam146
Copy link
Contributor

The ClusterRoleBinding 'openshift-builds-operator' references a non-existent ClusterRole 'operator', leaving the ServiceAccount without permissions.

OLM automatically creates RBAC resources from the CSV's clusterPermissions section. Removing this manual ClusterRoleBinding allows OLM to properly manage permissions as intended.

…rRole

The ClusterRoleBinding 'openshift-builds-operator' references a non-existent
ClusterRole 'operator', leaving the ServiceAccount without permissions.

OLM automatically creates RBAC resources from the CSV's clusterPermissions
section. Removing this manual ClusterRoleBinding allows OLM to properly
manage permissions as intended.

Signed-off-by: ayushsatyam146 <[email protected]>
Copy link
Contributor

@hasanawad94 hasanawad94 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@ayushsatyam146 just for clarification.
This ClusterRoleBinding was not binding this ClusterRole: config/rbac/role.yaml

@ayushsatyam146
Copy link
Contributor Author

@hasanawad94 OLM creates ClusterRoles with generated names from the CSV, not config from the operator hence this ClusterRole doesn't get created while installing the operator.

Copy link
Contributor

@hasanawad94 hasanawad94 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@sayan-biswas
Copy link
Contributor

@ayushsatyam146 How's the role mapped to a service account in that case?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants