Skip to main content
Version: 1.3.0

Console tour

The web console is a server-rendered Qute and HTMX application. It is the supported operator surface; it is not a single-page application.

The console never talks to storage on its own; it records intent and shows what the reconcile loop observed. Login is delegated to Keycloak, cluster credentials come from Vault by path, and durable state lives in PostgreSQL.

AreaUse it for
HomeLast reconcile, fleet summary, safety state, and recent alerts
InventorySource candidates and managed, adopted, or suspended relationships; each relationship detail carries a free-text operator note
InfrastructureClusters, SVM pairs, discovery, reachability, and safety controls
PolicyReplication profiles, automation profiles, volume groups, and exclusions
ApprovalsProposed actions, approvals, rejections, backlog, and Apply progress
Profile bindingBind, rebind, or unbind an adopted relationship's automation profile — authorizing profile-bounded destination fill/grow and approval-gated cleanup, without taking creation ownership
CapacityTwo views: Overview — Protected, Unprotected, Orphaned, and Excluded exposure (volumes, provisioned, physical); and By automation profile — the same figures per profile, searchable and paginated, with a drill-down into every bound volume
NotificationsActionable transitions with severity-aware coalescing
AuditWho changed configuration or authorized work, and when

A useful operating rhythm​

  1. Start at Home and confirm the last run completed observation.
  2. Inspect critical notifications before reviewing proposals.
  3. Review Inventory for new identities and unexpected adopted or suspended relationships.
  4. Review Approvals and the payload of every destructive proposal.
  5. Return after the next reconcile to confirm Apply or the new skip reason.
  6. Use Audit when reconstructing a decision.

The UI reads live operational fields such as lag, transfer state, and capacity when a page needs them. DonkeyFleet does not keep a table that mirrors ONTAP.