Section Overview
Nodes
Nodes are the runtime hosts attached to StackShift through the agent.
Node overview
What a node is, what the agent does, and what node health means in StackShift.
Goal
Understand nodes as runtime machines with operational state, not just a list in the UI.
Expected result
You understand how StackShift reasons about node readiness and workload placement.
BYOCloud overview
Connect customer-owned cloud accounts to StackShift, provision cloud-backed nodes, and operate them through the same node workflows used elsewhere in the product.
Goal
Understand the current BYOCloud workflow, supported providers, and the node-scoped operating model StackShift exposes today.
Expected result
You understand BYOCloud as a current StackShift node workflow for customer-owned infrastructure, including provisioning and ongoing node operations.
Connect a BYOCloud node
Save provider credentials, choose a tested region and StackShift tier, and wait for the provisioned cloud node to become healthy and schedulable.
Goal
Walk from saved provider credentials to a healthy BYOCloud node in the Nodes page.
Expected result
A BYOCloud node is provisioned and ready to host projects, stacks, or database flows once healthy.
BYOCloud cloud resources
Manage provider-backed node resources such as volumes, snapshots, placement metadata, stable public IPs, refresh, retry, reboot, and delete actions from the node detail surface.
Goal
Explain the current BYOCloud cloud resource and node operation surface available from the Nodes page.
Expected result
Operators can provision and operate BYOCloud nodes and their supported provider-backed resources directly from StackShift.
Install the agent
Bootstrap a new node and understand what the install command is doing on the target host.
Goal
Install the agent cleanly and know how to verify success on the host itself.
Expected result
The node is attached and the agent is running.
Upgrade the agent
Use the maintenance-first path to move an existing node to a newer agent version.
Goal
Update the node agent without leaving it in a confused scheduling state.
Expected result
The node reports the expected agent version and can safely leave maintenance.
Maintenance mode
Use maintenance as a safety control before upgrades or disruptive host changes.
Goal
Keep nodes out of the scheduler when you are about to perform risky host-level work.
Expected result
Node lifecycle work happens with fewer accidental scheduling side effects.
Node health, diagnostics, and deletion
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.
Expected result
Node cleanup and diagnostics become deliberate, not reactive.