Pause any stack without destroying the data or configuration. Pausing a stack saves cloud provider costs, and the stack can be deployed again when needed without rebuilding the stack.
For this use case, use the snapblocs pause and resume features instead of a teardown.
See the benefits of pausing a stack here.
Note that your cloud account will be charged since you deployed a stack. It is important to teardown your stack when you don't need to keep running to avoid unnecessary charges on your cloud account.
To pause a stack:
Once the stack is paused, all Kubernetes worker nodes will be released (It becomes 0 worker nodes) except the Kubernetes control plane. During the paused state, no component applications will be accessible as those pods were terminated. But the Kubernetes volumes will remain so that no data will be lost during the paused state. When the stack is resumed, those will be reattached to newly created worker nodes.
(Optionally) Click "Provision Log" to browse the pause process.