Nodes
BYOCloud resource add-ons
Live with caveatsManage provider-backed node resources such as volumes, snapshots, placement metadata, and stable public IP actions from the node-scoped cloud resources surface.
Goal
Explain the Phase 3 BYOCloud add-ons that deepen node operations without turning StackShift into a cloud console.
Current status
This area is real and usable, but the docs are intentionally calling out operational or UX limits that still matter.
Workflow
- 1Open the Cloud resources section on a BYOCloud node.
- 2Create, inspect, detach, or safely delete provider-backed volumes where supported.
- 3Create and review volume snapshots where the provider supports snapshots.
- 4Review placement, addressing, and static IP state directly from the node detail surface.
Current provider support
- AWS: EBS volumes, EBS volume snapshots, VPC/subnet/AZ metadata, Elastic IPs
- DigitalOcean: block storage volumes, volume snapshots, region/network metadata, Reserved IPs
- Hetzner: cloud volumes, location metadata, Floating IPs; attached-volume snapshots are intentionally unsupported
How to read the feature boundary
These are node add-ons and operational cues, not a general-purpose storage or networking product. StackShift only exposes the provider details that materially improve scheduling clarity, cleanup, reconciliation, and support.
Resource actions move through explicit lifecycle states and reconciliation. A successful request means StackShift accepted the action, not necessarily that the provider-side resource has finished changing state yet.
Expected result
Operators can handle the common cloud-backed node relationships StackShift supports without dropping into the provider console for every action.
Common failures
- Volume is still attached during delete
- Snapshot is still creating
- Static IP quota is exhausted
- Provider placement or address metadata drifted