Loupe

Editing and actions

YAML editing with a diff before every apply, operator actions behind confirmations, and per-context write guards.

The manifest view with syntax highlighting

YAML

  • The YAML view writes back with a full replace, so a concurrent modification is rejected by the API server rather than silently overwritten.
  • A diff is shown before every apply.

Actions

Scale, rollout restart, delete, cordon and drain are available on the objects they apply to, each behind a confirmation — and hidden entirely where RBAC would refuse them, so a button you can see is one you can use.

Guards

Each context carries a write guard, chosen from Writes in the status bar:

SettingGuardEffect
Allowed—Writes go through after their normal confirmation.
Confirm eachProtectedEvery write is confirmed by typing the context's name.
RefusedRead-onlyWrites are refused outright.

The guard is stored per context, shown in the status bar, and tints it — so a production cluster does not look like a local one.

A guard is Loupe's own safeguard, not RBAC. It does not change what your credentials are allowed to do, only what Loupe will send.

On this page