Is your feature request related to a problem? Please describe.

Currently, the Redis Operator deploys with ClusterRole and ClusterRoleBinding, but we can't use the ClusterRole and ClusterRoleBinding in our k8s cluster. Since our use case involves managing all Redis Operator and related resources within a single namespace, we require a configuration option to use Role and RoleBinding instead.

Describe the solution you'd like

I propose adding a configurable option in the Helm chart to select between ClusterRole/ClusterRoleBinding and Role/RoleBinding. By default, the configuration should use ClusterRole/ClusterRoleBinding for backward compatibility and broader cluster-wide operations. Users who need namespace-specific permissions should be able to set a scope value to switch to Role/RoleBinding.

What version of redis-operator are you using?

redis-operator version: 0.20.3