KubeBolt docs
ENES GitHub

Configuration

RBAC & Permissions

What KubeBolt may do in your cluster: the credentials it uses, the ClusterRole the chart creates, how it probes its permissions, and how the UI degrades when they are narrow.

On this page
  1. Which credentials KubeBolt uses
  2. The chart’s ClusterRole
  3. Permission Detection
  4. Access Levels
  5. Frontend Behavior
  6. The agent’s RBAC tiers
  7. API Endpoint

This page is about what KubeBolt may do in the cluster. What each KubeBolt user may do in KubeBolt — the Viewer, Editor and Admin roles — is covered in Authentication. An action needs both: a role that allows it and cluster permissions that allow it.

KubeBolt never impersonates the signed-in user. Every read and every action runs with KubeBolt’s own Kubernetes credentials, so those credentials are the ceiling for everyone — Kobi included.

Which credentials KubeBolt uses

ConnectionCredentialsWhere the scope is set
In-cluster (the Helm chart)The chart’s ServiceAccountThe chart’s ClusterRole — below
Kubeconfig context (on disk or uploaded in the UI)Whatever user the context carriesYour kubeconfig and the cluster’s RBAC
Agent-connectedThe agent’s ServiceAccountThe agent chart’s rbac.mode — below

On KubeBolt Cloud every cluster is agent-connected.

The chart’s ClusterRole

With rbac.create=true (the default), the kubebolt chart binds a ClusterRole to its ServiceAccount. It grants:

GrantWhy
get / list / watch on core, apps, batch, networking, policy, autoscaling, storage, RBAC, discovery and Gateway API resources, plus optional CRDs (cert-manager, Argo CD, VPA, Cilium, External Secrets, Trivy, Kyverno policy reports)Inventory, topology, insights, the Security dashboard
get / list on metrics.k8s.io pods and nodesLive CPU and memory from Metrics Server
create on selfsubjectaccessreviewsThe permission probe below
create on pods/exec, pods/portforward, pods/evictionTerminal, file browser, port-forward, evict
create / update / delete on workloads, Jobs, CronJobs, Pods, Services, PVCs, NetworkPolicies, Ingresses, HPAs, StorageClasses and Gateway API objects (plus patch on workloads, Jobs, CronJobs, HPAs and Gateway API objects); get / update on deployments/scale and statefulsets/scaleEdit YAML, create from a manifest, restart, scale, delete
create / update / delete on Secrets, ConfigMaps, ServiceAccounts, RBAC objects; create on Namespaces and DaemonSets; escalate / bind on Roles and ClusterRolesThe first-boot admin-password Secret, agent ingest-token Secrets, and the agent install wizard
create on tokenreviewsOnly with agentIngest.rbac.enableTokenReview=true (default): agents that authenticate with their projected ServiceAccount token

The role grants no writes on Nodes and no patch on core kinds such as Services, ConfigMaps and Secrets. On the cluster KubeBolt runs in, cordon, uncordon and drain, and label or annotation edits on those kinds, come back 403 unless you bind an extra ClusterRole to the chart’s ServiceAccount that grants them.

To run KubeBolt with less, set rbac.create=false and bind your own ClusterRole (or Roles) to the chart’s ServiceAccount — named after the release by default (kubebolt for a release called kubebolt), or whatever you set in serviceAccount.name. A read-only role works: KubeBolt probes what it was given, the UI degrades as described below, and write actions come back 403 from the apiserver. Keep create on selfsubjectaccessreviews, or the probe cannot tell what you granted.

Permission Detection

KubeBolt probes its permissions when it connects to a cluster — any cluster, whichever credentials it uses:

The core probe runs once per connection. After you change RBAC, restart the KubeBolt API so it reconnects and probes again.

Access Levels

LevelBackendFrontend
Cluster-admin or full readInformers start for every typeFull UI, no restrictions
Cluster-wide, some types deniedInformers for permitted types onlyRestricted items dimmed, “Limited access” banner
Namespace-scoped (RoleBindings)Per-namespace informer factories, results mergedResources from the permitted namespaces only

Frontend Behavior

Troubleshooting walks through the banner on an agent-connected cluster.

The agent’s RBAC tiers

On agent-connected clusters you choose the agent’s scope up front with --set rbac.mode= on the agent chart, and KubeBolt then probes that scope like any other:

More on choosing a tier in Connecting clusters.

API Endpoint

GET /api/v1/cluster/permissions returns the probe result for the selected cluster, keyed by resource type. Each entry carries resource, group, canList, canWatch and canGet, plus namespaceScoped and namespaces when access comes from RoleBindings, and absent for an optional CRD the cluster doesn’t serve.

{
  "pods":   { "resource": "pods", "group": "", "canList": true, "canWatch": true, "canGet": true },
  "nodes":  { "resource": "nodes", "group": "", "canList": false, "canWatch": false, "canGet": false },
  "argocdapps": { "resource": "applications", "group": "argoproj.io", "canList": false, "canWatch": false, "canGet": false, "absent": true }
}