KubeBolt docs
ENES GitHub

Core Concepts

Resource Views

26 resource list views with search, pagination and live metrics, plus Namespaces, Events, cluster RBAC and Helm releases, and a tabbed detail page for every object.

On this page
  1. Supported resources
  2. Resource detail views
  3. Actions
  4. Monitor charts on long ranges
  5. Revealing a Secret value

Supported resources

KubeBolt has 26 resource list views, grouped in the cluster sidebar the same way as below. Each supports search, namespace filtering, server-side pagination (50 per page) and, where it applies, live CPU and memory from Metrics Server. The sidebar shows a count next to each and marks the ones your identity cannot list (see RBAC).

Sidebar groupResources
PinnedPods, Nodes (plus Insights, Applications and, on KubeBolt Cloud, Autopilot)
WorkloadsDeployments, StatefulSets, DaemonSets, Jobs, CronJobs
TrafficServices, Ingresses, NetworkPolicies, Cilium Policies (CiliumNetworkPolicies), Cilium Cluster Policies (CiliumClusterwideNetworkPolicies), PodDisruptionBudgets, Gateways, HTTPRoutes, Endpoints (EndpointSlices)
StoragePVCs, PVs, StorageClasses
ConfigConfigMaps, Secrets (keys by default — values only through the audited reveal), Service Accounts, HPAs
ExtensionsCertificates (cert-manager), ArgoCD Apps, VPA (VerticalPodAutoscalers)

The Cluster group adds three views that aren’t plain lists: Namespaces, Events, and RBAC (ClusterRoles and ClusterRoleBindings), next to Clusters, where clusters are added, renamed and removed (Multi-Cluster). Extension and Cilium views show up with data only when the CRD is installed; a missing CRD is reported as a neutral “Optional integrations not detected” note, not as a permission problem, and a CRD installed later is picked up within two minutes. ReplicaSets have no list of their own: they appear in a Deployment’s history, the Related tab and the Cluster Map.

Namespaces pages 50 at a time, counts every namespace and filters by name. When KubeBolt’s credentials may not list events, Events shows Access Restricted instead of failing, and Kobi is told that seeing no events does not mean there are none.

Applications lists the Helm releases in the cluster: status, chart, values, manifest, notes, the resources a release owns and its revision history. It is read-only: KubeBolt does not install, upgrade or roll back Helm releases. See Helm Applications.

On a metrics-only cluster (an agent that ships metrics but gives KubeBolt no API access) these views are off; the dashboard still works.

Resource detail views

Each resource has a tabbed detail page at /:type/:namespace/:name (_ stands in for the namespace of cluster-scoped resources). Available tabs vary by type:

A Deployment: actions, pods, history and events without leaving the page.
A Deployment: actions, pods, history and events without leaving the page. KubeBolt 2.1.1
ResourceTabs beyond Overview, YAML and Events
PodsContainers, Logs, Terminal, Files, Volumes, Related, Monitor
Deployments, StatefulSets, DaemonSetsPods, Logs, Terminal, Related, History, Monitor
JobsPods, Logs, Related
CronJobsJobs, Related
ServicesRelated
NodesPods, Monitor
NetworkPolicies, Cilium policies, PodDisruptionBudgetsMatched Pods, Related
PersistentVolumeClaimsMonitor

What each tab does:

Actions

The toolbar above the tabs has Describe (the kubectl describe output, hiding the same values as the YAML tab) and, when Kobi is configured, Ask Kobi, for every role. Writes need Editor, deletes need Admin, and all of them are audited:

ResourceActions
Deployments, StatefulSets, DaemonSetsSet image, Restart; under Actions ▾: Set resources, Set env, Scale (not DaemonSets), Pause / Resume rollout (Deployments). Roll back from the History tab
PodsRestart (deletes the pod for its controller to recreate); under Actions ▾: Evict pod (honours PodDisruptionBudgets), Debug (an ephemeral debug container). Port-forward from a container’s ports
CronJobsTrigger now, Suspend / Resume
NodesCordon / Uncordon; Drain (Admin)
SecretsReveal (see below)
Every kindEdit metadata (labels and annotations), Delete (Admin)

On a cluster reached through the agent, writes, exec, port-forward and the file browser need the agent in operator mode; in reader mode they come back as permission errors. See Connecting clusters.

Monitor charts on long ranges

A history chart draws one point per interval, and the interval grows with the range:

RangeOne point every
5m, 15m, 1h15 or 30 s
6h2 min
24h10 min
7d1 h
14d2 h
30d6 h

From 6h up, the CPU and memory charts of pods, workloads and nodes draw the highest value inside each interval, read once a minute, so a spike between two points still shows. The stats beside those charts change names to match:

Kobi’s get_workload_metrics reads the same peaks and says when the maximum happened.

Network charts are not peaked: each point is the rate over the minute before it, so on a long range a burst between two points doesn’t show.

Size a request from typical use (the rightsizing P95) and a memory limit’s headroom from max.

A pod that runs with hostNetwork shares its node’s network, so it has no traffic of its own to chart. Its Monitor tab shows Uses the node’s network with a link to each node’s Monitor tab, and so does a workload whose pods run that way. Since agent 1.4.8 such a pod sends no pod network at all; its traffic is counted once, on the node. See Compatibility.

Revealing a Secret value

The YAML view never shows Secret values. When you actually need one — validating a rotation, say — there is a separate, deliberately narrow path instead of dropping to kubectl get secret -o yaml | base64 -d:

POST /api/v1/resources/secrets/{namespace}/{name}/reveal

It is designed to be auditable rather than convenient:

Request body: {"keys": ["…"], "reason": "…"}. Omitting keys reveals every key and audits the breadth as <all>. Values that are not printable UTF-8 come back as a sha256 plus a byte count rather than as garbled text.