ORD1 tenant cluster customers do not have cluster-scoped access (cannot read ClusterRoles, ClusterRoleBindings, StorageClasses, etc.). Therefore it makes sense to remove those items from the dashboard:
The rationale being, if customers are not able to view these resources, we shouldn't tease them / confuse them by giving them a button to do so.
They can view CustomResourceDefinitions (which are cluster scoped), so we should keep those.
ORD1 tenant cluster customers do not have cluster-scoped access (cannot read ClusterRoles, ClusterRoleBindings, StorageClasses, etc.). Therefore it makes sense to remove those items from the dashboard:![Screenshot 2024-01-04 143520](https://github.com/coreweave/dashboard/assets/8888572/4a85b223-fdd8-48b4-bf7a-86929b004f7b)
The rationale being, if customers are not able to view these resources, we shouldn't tease them / confuse them by giving them a button to do so.
They can view CustomResourceDefinitions (which are cluster scoped), so we should keep those.