Documentation

Node health, diagnostics, and deletion

Read node diagnostics correctly and understand when deletion is safe or blocked.

Try StackShiftRead the overview

Nodes

Node health, diagnostics, and deletion

Live

Read node diagnostics correctly and understand when deletion is safe or blocked.

Goal

Avoid deleting or trusting a node without checking the operational details that matter.

Current status

Live

This area is documented as current, user-reliable behavior.

Workflow

  1. 1Use CPU, memory, disk, Docker, and Caddy readiness as runtime diagnostics.
  2. 2Review workload attachment and maintenance state before deletion.
  3. 3Treat agent-unknown or stale-heartbeat nodes as operationally different from healthy nodes.

Deletion expectations

  • Node deletion is guarded by confirmation rather than being a one-click destructive action.
  • A node with attached workloads or unresolved maintenance concerns should be reviewed before deletion.
  • Diagnostics and workload context matter more than a single status badge when deciding whether a node is safe to remove.

Expected result

Node cleanup and diagnostics become deliberate, not reactive.