How to pause a stack

How to pause a stack

Once deploying a stack following How to deploy a stack, you can pause the stack.
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:
  • Click the "Pause" button on the top of the Stack configuration page. (It would take up to a few minutes to fully pause the stack) The stack status will be changed to Paused. 
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.

What's Next?



    • Related Articles

    • What is a Stack

      A stack is an instance of a Platform built from an architecture blueprint that you can manage as a single unit. Platforms provide building blocks that are reused in a large number of products and services. It has a set of components that can be ...

    • How to deploy a stack

      Once configuring a stack following here, you can deploy the stack. To deploy a stack: Click the "Deploy" button on the top of the Stack configuration page. (It would take up to 20 minutes to fully deploy the stack) The stack status will be changed to ...

    • How to resume a stack

      Once pausing a stack following here, you can resume the stack. 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 ...

    • Configure Stack

      Before proceeding, click here to set up AWS configuration. ​ Configure a stack before deploying it. To configure a stack: Go to the Stacks menu. Click "Configure new stack." Select "Default" for the project, or select any project for the new stack. ...

    • How to move a stack

      Once configuring a stack following here, you can move the stack configuration from the project where the stack was created to a different project.  Once a stack has been configured for one project, an authorized user can easily move the stack ...