Documentation
Browsing and editing
One informer-backed view per resource type, and an inspect drawer that edits the live object.
How the tables are built
Discovery builds a catalog of what the cluster serves. Each type you subscribe to gets a dynamic informer whose cache is projected into rows, so a CRD needs no per-type code to get a working view.
The socket sends one snapshot and then deltas keyed by uid. Informers strip managedFields before caching, so the rows stay small.
- A field-aware filter, completed from what the cluster actually reported.
- Namespace scope, carried across views.
- A badge on objects that are failing, before you open one.
- Bulk restart and bulk delete from a selection.
Rows answer to the keyboard: arrows move between them, Home and End jump to the ends, Enter opens the inspector on the row, Space selects it for a bulk action, and Cmd or Ctrl with Enter opens the row and moves you into the inspector. Settings publishes the full list under Keyboard, and ? shows it from anywhere.
The inspect drawer
Metadata, conditions, events and the live YAML in Monaco, with completion driven by the cluster's own OpenAPI so your CRDs are covered too. Changes go back through server-side apply. A draft you are editing survives a background reload.
Secret values arrive masked. Reveal them one key at a time, and the reveal drops the moment you select something else.
Comparing
Any object can be put beside the same object in another context, or a whole kind can be compared at once with a verdict per object: same, differs by so many lines, or present on only one side.
Both sides lose status, managedFields and the rest of what the server assigns first, so what differs is what you authored.
Write actions
- Scale, and rollout restart.
- Cordon and uncordon.
- Drain, which shows its eviction plan first: what it evicts, what it leaves, what it blocks and why.
- CronJob suspend, resume and run now.
A cluster you mark as protected requires the object name typed out before a destructive action runs. Deleting, draining, scaling to zero and uninstalling are the actions it covers.
A cluster you have not opened before offers protection once, as a notice you can accept or dismiss without leaving what you were doing. The answer is remembered for that cluster, and the padlock in the top bar turns it on or off later.