[Bug] KubeRay tries to create ClusterRoleBinding when singleNamespaceInstall and rbacEnable are set to true

[anshulomar]

Search before asking

• I searched the issues and found no similar issues.

KubeRay Component

ray-operator

What happened + What you expected to happen

After #1106 and #1162 were merged, I provided the following config combination:
rbacEnable: true
crNamespacedRbacEnable: false
singleNamespaceInstall: true
watchNamespace:
- ns1

I expected KubeRay to not create cluster-scoped resources and to not create roles and rolebindings in "ns1" namespace. But I observed that KubeRay tries to create ClusterRoleBinding. Looking at the code https://github.com/ray-project/kuberay/blob/master/helm-chart/kuberay-operator/templates/rolebinding.yaml#L1-L2, it will always create a ClusterRoleBinding if rbacEnable is set to true.

Reproduction script

1. Create a Kind cluster
2. Install KubeRay operator via Helm and provide following config combination:
   rbacEnable: true
crNamespacedRbacEnable: false
singleNamespaceInstall: true
watchNamespace:
- ns1
3. Observe that KubeRay tries to create a ClusterRoleBinding

Anything else

This problem occurs everytime. I think the logic for creating ClusterRoleBinding should be the same as that for ClusterRole: https://github.com/ray-project/kuberay/blob/master/helm-chart/kuberay-operator/templates/role.yaml#L1C1-L1C1.

Are you willing to submit a PR?

• Yes I am willing to submit a PR!

[anshulomar]

@kevin85421 could you, please, take a look? Thanks.