Resource Management

Browse, inspect, and operate on 27 Kubernetes resource types — all updated in real time via the Kubernetes watch API.

This page focuses on how Krust handles Kubernetes resources during daily operations. It is less about a raw resource inventory and more about how state changes, inspections, and routine actions behave in practice.

Supported Resources

Workloads

• Pods
• Deployments
• StatefulSets
• DaemonSets
• ReplicaSets
• Jobs
• CronJobs
• Horizontal Pod Autoscalers (HPAs)

Networking

• Services
• Ingresses
• Gateways
• NetworkPolicies

Config

• ConfigMaps
• Secrets

Storage

• PersistentVolumes (PVs)
• PersistentVolumeClaims (PVCs)
• StorageClasses

RBAC

• Roles
• ClusterRoles
• RoleBindings
• ClusterRoleBindings
• ServiceAccounts

Cluster

• Nodes
• Namespaces
• PodDisruptionBudgets
• Custom Resource Definitions (CRDs)
• Custom Resource instances

Package Management

• Helm Releases

Real-time Watchers

Every resource type is backed by the Kubernetes watch API. When a pod restarts, a deployment scales, or a secret changes, the update appears in Krust instantly — no manual refresh needed. Watchers reconnect automatically on network interruption with exponential backoff.

The practical outcome is that navigation feels read-through rather than request-driven. You spend less time waiting for each screen to refresh because most state is already in memory.

Operations

Krust supports the full range of day-to-day Kubernetes operations directly from the GUI:

• Delete — Remove any resource with confirmation dialog
• Scale — Adjust replica count for Deployments, StatefulSets, and ReplicaSets
• Restart — Trigger a rolling restart by patching the pod template annotation
• Suspend / Resume — Toggle CronJob suspension on and off
• Evict — Evict pods from a specific node for maintenance

These operations are intentionally biased toward common operator tasks. Krust is not trying to replace declarative workflows or GitOps; it is shortening the path for inspection, remediation, and verification.

Inspector

Click any resource name to open the detail inspector. The inspector shows:

• Full resource details and metadata
• Conditions and status
• Events related to the resource
• Container specs (image, ports, resources, probes)
• Volume mounts and volume definitions
• Environment variables and config references

The inspector is most useful when the problem spans several layers at once: status conditions, recent events, image version, probes, resource limits, and mounted config.

Bulk Operations

Select multiple resources with Cmd+click, then perform batch operations on the entire selection. Supported bulk actions include delete, restart, and scale — each with a confirmation dialog showing exactly which resources will be affected.

This is designed for cases like restarting multiple workloads after a shared config issue or scaling a subset of services during an incident.

Context Menus

Right-click any resource row to see a context menu with actions specific to that resource type. Pods show exec, logs, and delete; Deployments show scale, restart, and delete; CronJobs show suspend/resume — and so on for every resource kind.

That keeps the common path short: select the object, act on the object, verify the result. The goal is to reduce command recall, not to hide what Kubernetes is doing underneath.

When This Page Matters Most

• When you manage many resource kinds and want a consistent inspection model.
• When you need real-time state without repeated manual refreshes.
• When routine operational actions should be fast but still explicit.