Why does Z2JK require cluster roles and cluster role bindings instead of roles and role bindings?

Can some one help me to understand why we need cluster roles and cluster role bindings instead of roles and role bindings while deploying Z2JK in Kubernetes? Currently I dont have cluster level access. I am having access to only one namespace.

It’s only used by the user scheduler - since it needs to schedule pods, it needs access to everything on the network. You can disable that if you want to run in a single namespace. More details on how to disable it at Optimizations — Zero to JupyterHub with Kubernetes documentation