Skip to content
lumenDocs

Team access

Source: src/routes/cluster/TeamAccess.tsx, src-tauri/src/k8s/rbac_admin.rs, src-tauri/src/k8s/rbac_details.rs at v0.18.0.

Find access control in a cluster workspace. Reading the screen requires access to the relevant service accounts and RBAC objects. Provisioning or changing access requires the corresponding create, update, token, and delete permissions and is a cluster mutation.

  1. Review the target cluster, namespace, identity, role, and expiry before selecting Provision access.
  2. Download the generated kubeconfig only to its intended secure destination. A download contains usable access material.
  3. Use the existing identity controls to Renew, Re-download, Rotate, or Revoke. Rotation invalidates the previous credential; revocation removes the managed access represented by the screen.
  4. Verify the new credential from an appropriate environment and confirm the intended old credential no longer works after rotate or revoke.

Protected-context and read-only controls can block these actions. Kubernetes authorization and admission remain authoritative. Lumen cannot establish how a downloaded credential is stored, transmitted, or deleted after it leaves the app.