Before reporting an issue

[x] I have read and understood the above terms for submitting issues, and I understand that my issue may be closed without action if I do not follow them.

Area

operator

Describe the bug

The ClusterRoleBinding uses a hardcoded namespace, which causes the binding to fail if deploying the Operator to a namespace other than keycloak.

The Role and ClusterRole definitions are also missing metadata labels.

Version

Nightly

Regression

[ ] The issue is a regression

Expected behavior

The guides should detail that the ClusterRoleBinding should be updated when using a namespace other than "keycloak".

Actual behavior

The current instructions in the guides will cause the Operator deployment to not function as expected as CustomResourceDefinitions can not be retrieved when the ClusterRoleBinding is incorrect.

How to Reproduce?

With the nightly build:

kubectl -n <custom-namespace> apply -f https://raw.githubusercontent.com/keycloak/keycloak-k8s-resources/refs/tags/nightly/kubernetes/kubernetes.yml

This will cause the Operator to receive permissions issues as it can retrieve CRDs as expected as the binding failed.

Anything else?

No response