Cluster Nodes
Cluster Nodes is the topology inventory for member identity, version, registry state, health, uptime, DNS totals, last-seen time, probes, and removal.
Where to find it: SDM root sidebar > Cluster Nodes.
Available to: root.
What this page does
Use this page to prove which nodes belong to the deployment and whether each member is registered and healthy. It also provides guarded removal and detach controls; it does not create a public cluster API.
Before you start
Refresh the page, confirm the local node IP and join key custody, and check backup/monitor state before removal. Determine whether the target is a remote member or the current node because the outcomes differ.
Node columns
- Node / IP / Version: identity and software level.
- Registry / Health: membership state and current probe result.
- Uptime: observed service or node uptime.
- DNS Zones / Records: data totals reported for the member.
- Last seen: recency of the latest healthy communication.
- Actions: probe, remove remote member, or detach this node where the current state allows it.
Controls and fields
| Control, Field, Or Section | What It Does | What It Affects | Recommended Usage |
|---|---|---|---|
| Refresh | Reloads membership, join key, self IP, node table, and health snapshots. | Does not change the cluster; it refreshes operational data. | Use before removing a node or checking a suspected peer outage. |
| Cluster Join Key | Displays current join material when available. | Used by another server to join this cluster. | Treat as sensitive and rotate through the normal cluster workflow if exposed. |
| Copy join key | Copies the join key to the clipboard. | No backend change. | Copy only into a secure deployment channel. |
| Current Node IP | Shows the local node address used by cluster workflows. | Helps identify which server the operator is currently managing. | Confirm before removing self or sharing node details. |
| Copy current node IP | Copies the local node IP. | No backend change. | Use when adding this node to monitoring or cluster documentation. |
| Node column | Shows node label/identity. | Human-readable cluster member identification. | Compare with expected topology inventory. |
| IP column | Shows peer address or host. | Network endpoint used to reach that node. | Check reachability if health is degraded. |
| Registry column | Shows whether the node is registered and how it is classified. | Indicates membership state. | Investigate nodes that are missing or stale before removal. |
| Health column | Shows aggregated health result from monitor/probe data. | Reflects service, API, TLS, and sync signals where available. | Open Monitor for detailed checks when health is not healthy. |
| Uptime column | Shows how long the node or service has been running. | Helps identify recent restarts or unstable nodes. | Short uptime during incidents may explain sync or DNS interruptions. |
| DNS Zones / DNS Records columns | Show DNS inventory size visible for that node. | Helps detect sync drift or incomplete node state. | Compare counts across peers when troubleshooting replication. |
| Last seen | Shows when the node was last observed. | Identifies stale or disconnected peers. | Treat old last-seen values as a sign to probe before acting. |
| Probe | Runs a targeted reachability/health check for the node. | Collects current status without removing or changing the node. | Use before opening a network or service incident. |
| Remove / Remove Self | Removes a peer or detaches the local node after confirmation. | Changes cluster topology and requires removed nodes to rejoin/create before participating again. | Use only for retired, rebuilt, or intentionally detached nodes. |
How to read the result
| Status Or Message | Meaning | What To Check |
|---|---|---|
| Active / healthy | The node is registered and responding normally. | No immediate action; keep monitoring. |
| Pending / awaiting refresh | The UI is waiting for updated node detail or the node is not fully established. | Refresh or probe, then check Monitor if it remains pending. |
| Unhealthy / down / unavailable | The node failed a health, service, API, TLS, or reachability check. | Open Monitor, inspect logs, and verify network/TLS before removing. |
| Removed from registry | The UI marked a removed node locally after the removal action. | Confirm remaining nodes and update external monitoring. |
Safety notes
- Removing nodes changes cluster topology and may require manual rejoin/recreate work on the removed server.
How to use it
- Select Refresh and compare every member's registry and health state.
- Probe a suspect node before declaring it offline.
- For removal, confirm the exact target and the effect on remaining DNS capacity.
- If removing the current node, follow the hard-detach confirmation and expect standalone state.
- Recheck Dashboard, Cluster Nodes, Monitor, and DNS resolution after topology changes.
Result and next check
The node list matches the intended topology, active members pass probes, and removed members no longer participate. A detached local node must be created or joined again before it can re-enter the deployment.
Theme color