[BUG] Operator fails to start when using useRoleBindings parameter in the chart

[sdiamond2]

What is the bug?

After the controller has been started, it fails with the following error for each opensearch CRD:
E0127 15:19:43.100647 1 reflector.go:148] pkg/mod/k8s.io/[email protected]/tools/cache/reflector.go:231: Failed to watch *v1.OpensearchUserRoleBinding: failed to list *v1.OpensearchUserRoleBinding: opensearchuserrolebindings.opensearch.opster.io is forbidden: User "system:serviceaccount:XXXX:opensearch-operator-controller-manager" cannot list resource "opensearchuserrolebindings" in API group "opensearch.opster.io" at the cluster scope.

After every 5-6 minutes, the pod will be entering a crashloopbackoff status, and restart.

How can one reproduce the bug?

In order to reproduce this bug, you need to define a namespace in watchNamespace and set useRoleBinding to true when deploying the chart.

What is the expected behavior?

Since I am deploying into a namaspace and I want to use the rolebinding, I would not expect the operator to look for the resource at the cluster level.

What is your host/environment?

Ubuntu 24.04

Do you have any screenshots?

N/A

Do you have any additional context?

Additionally, I confirmed with the CRD and the scope is namespaced.

[prudhvigodithi]

[Triage]
Adding @swoehrl-mw @evheniyt to please take a look.

[sdiamond2]

Thank you very much, looking forward to get an answer for this. I like this project, and I appreciate this option if it would work correctly, unless I missed something on my side.