Skip to main content

Access Mapping

The Access Mapping page is a read-only view of every Kubernetes binding and VMO IAM mapping PaletteAI VM Launchpad manages on your behalf. Use it to audit who has access to a given namespace and to trace which Kubernetes ClusterRole is bound to a specific user or group, without opening a kubectl shell.

Prerequisites​

  • A cluster created using VM Launchpad. Refer to Install VM Launchpad for guidance.

  • An account with the Platform Admin VMO role, or membership in a group mapped to Platform Admin.

Access Mapping Page​

From the left main menu, select Settings > Access Management > Access Mapping to view the resolved bindings.

Each row represents one binding. The columns describe who the binding applies to and what it grants.

ColumnDescription
SubjectThe user or group the binding applies to.
TypeThe subject kind: User or Group.
K8s RoleThe Kubernetes ClusterRole the binding references. VM Launchpad marks built-in roles with a ClusterRole or Role pill.
Binding TypeThe Kubernetes binding kind. Common values are ClusterRoleBinding and RoleBinding.
VMO RoleThe VMO IAM role the binding resolves to (Platform Admin, Editor, Operator, or Viewer). An empty cell means the row represents a Kubernetes-only binding with no VMO IAM role attached.
NamespaceThe namespace the binding is scoped to. Rows with cluster-wide access show All Namespaces.

Select a column header to sort. Use the Filter rows search box to filter by any field, or use the Filters button to filter by subject type, namespace, Kubernetes role, or VMO role.

Show or Hide Columns​

Select the gear icon in the top right of the table to open the Show / Hide Columns panel. Toggle any column to show or hide it, or select Reset to defaults to restore the default column set.

How to Read a Row​

The Access Mapping table surfaces the two planes of access management in the same view.

  • Kubernetes bindings. A row with a value in K8s Role and Binding Type represents a real ClusterRoleBinding or RoleBinding in the cluster. This grants direct Kubernetes access (kubectl and KubeVirt API calls) to the subject.

  • VMO IAM mappings. A row with a value in VMO Role represents a mapping from the subject to a VMO platform role. This controls what the subject can view and do in the VM Launchpad UI.

  • Dual-plane grants. Rows with values in both K8s Role and VMO Role are grants VM Launchpad created through the Users or Groups pages, where a single action creates both the Kubernetes binding and the VMO IAM mapping.

info

Local users bypass the OIDC access chain and use the pod's ServiceAccount token to reach the Kubernetes API. They carry full cluster access and do not appear as bindings in the Access Mapping table. Refer to Auth Modes for details.

Auth Modes​

The access chain that produces the bindings on this page depends on how VM Launchpad is deployed.

ModeDescription
KeycloakDirect OIDC with the appliance's built-in Keycloak. The browser redirects to Keycloak, receives tokens, and VM Launchpad creates a session.
Palette or VerteX proxyThe Palette or VerteX proxy sits between the browser and the identity provider. Tokens flow through the proxy before reaching VM Launchpad.
LocalNo external identity provider. The browser sends credentials directly to VM Launchpad, and the session uses the pod's ServiceAccount token for Kubernetes access.

Next Steps​

  • Grant a user access. Refer to Users.

  • Grant a group access. Refer to Groups.

  • Review the built-in VMO roles and their permissions. Refer to VMO Roles.