Role to ClusterRole Mapping
NVIDIA Run:ai maps each predefined role to Kubernetes ClusterRoles. Users who authenticate to the cluster with their NVIDIA Run:ai identity and access it with kubectl receive these Kubernetes permissions in addition to the permissions that the role grants in the NVIDIA Run:ai platform. Use this page to see which ClusterRoles each role maps to and what each ClusterRole grants. For example, share it with your security team when reviewing access.
Note
This page covers the predefined roles listed in Roles. It does not cover legacy roles or roles used internally by the platform.
How Roles Map to ClusterRoles
When an access rule assigns a role to a subject, NVIDIA Run:ai binds the subject to up to five ClusterRoles. In the table, <role> is the name of the role, for example ai-practitioner.
The runai-<role>-ns ClusterRoles are aggregated ClusterRoles. Their rules combine the rules listed on this page with one additional ClusterRole, runai-additional-workload-gvks-read or runai-additional-workload-gvks-crud. NVIDIA Run:ai creates this additional ClusterRole at runtime, and it grants read or full access to every external workload type registered in the cluster.
Note
The runai-system-administrator-logs RoleBindings are created only in namespaces that already exist when NVIDIA Run:ai is installed or upgraded. If you install a component such as the GPU Operator after NVIDIA Run:ai, run a Helm upgrade of the NVIDIA Run:ai cluster chart to add the binding for the new namespace. The bindings are also not created when the chart is rendered with helm template, for example by GitOps tools such as Argo CD.
ClusterRoles per Role
Permissions per ClusterRole
Expand a role to see the API groups, resources, and verbs that each of its ClusterRoles grants.
To view the permissions on your own cluster, run:
System administrator
runai-system-administrator
Bound with a ClusterRoleBinding, cluster-wide, for every access rule.
runai-system-administrator-ns
Bound with a RoleBinding in each project namespace in the scope of the access rule, for every access rule.
This ClusterRole also aggregates runai-additional-workload-gvks-crud.
runai-system-administrator-runai
Bound with a RoleBinding in the runai namespace, for every access rule.
runai-system-administrator-runai-cs
Bound with a RoleBinding in the runai namespace, only for access rules scoped to the cluster or the account.
runai-system-administrator-logs
Bound with a RoleBinding in the runai-backend, runai-reservation, training-operator, knative, gpu-operator, and nim-operator namespaces. Each binding is created only if the namespace existed when NVIDIA Run:ai was installed or upgraded.
Used by the runai diagnostics collect-logs command, which collects pod logs from these namespaces and from the runai namespace for NVIDIA Run:ai support.
Department administrator
runai-department-administrator
Bound with a ClusterRoleBinding, cluster-wide, for every access rule.
runai-department-administrator-ns
Bound with a RoleBinding in each project namespace in the scope of the access rule, for every access rule.
This ClusterRole also aggregates runai-additional-workload-gvks-crud.
runai-department-administrator-runai
Bound with a RoleBinding in the runai namespace, for every access rule.
Department viewer
runai-department-viewer
Bound with a ClusterRoleBinding, cluster-wide, for every access rule.
runai-department-viewer-ns
Bound with a RoleBinding in each project namespace in the scope of the access rule, for every access rule.
This ClusterRole also aggregates runai-additional-workload-gvks-read.
runai-department-viewer-runai
Bound with a RoleBinding in the runai namespace, for every access rule.
Project administrator
runai-project-administrator
Bound with a ClusterRoleBinding, cluster-wide, for every access rule.
runai-project-administrator-ns
Bound with a RoleBinding in each project namespace in the scope of the access rule, for every access rule.
This ClusterRole also aggregates runai-additional-workload-gvks-crud.
runai-project-administrator-runai
Bound with a RoleBinding in the runai namespace, for every access rule.
AI practitioner
runai-ai-practitioner
Bound with a ClusterRoleBinding, cluster-wide, for every access rule.
runai-ai-practitioner-ns
Bound with a RoleBinding in each project namespace in the scope of the access rule, for every access rule.
This ClusterRole also aggregates runai-additional-workload-gvks-crud.
runai-ai-practitioner-runai
Bound with a RoleBinding in the runai namespace, for every access rule.
Data and storage administrator
runai-data-and-storage-administrator
Bound with a ClusterRoleBinding, cluster-wide, for every access rule.
runai-data-and-storage-administrator-ns
Bound with a RoleBinding in each project namespace in the scope of the access rule, for every access rule.
This ClusterRole also aggregates runai-additional-workload-gvks-read.
runai-data-and-storage-administrator-runai
Bound with a RoleBinding in the runai namespace, for every access rule.
runai-data-and-storage-administrator-runai-cs
Bound with a RoleBinding in the runai namespace, only for access rules scoped to the cluster or the account.
Editor
runai-editor
Bound with a ClusterRoleBinding, cluster-wide, for every access rule.
runai-editor-ns
Bound with a RoleBinding in each project namespace in the scope of the access rule, for every access rule.
This ClusterRole also aggregates runai-additional-workload-gvks-crud.
runai-editor-runai
Bound with a RoleBinding in the runai namespace, for every access rule.
Viewer
runai-viewer
Bound with a ClusterRoleBinding, cluster-wide, for every access rule.
runai-viewer-ns
Bound with a RoleBinding in each project namespace in the scope of the access rule, for every access rule.
This ClusterRole also aggregates runai-additional-workload-gvks-read.
runai-viewer-runai
Bound with a RoleBinding in the runai namespace, for every access rule.