Clone and move
Once a stack has been configured for one project, an authorized user can easily clone the stack configuration to a different project and then update the configuration (such as cluster parameters and target environment settings). The new cloned stack can then be deployed to staging or production environments.
Stacks can also be moved across projects while retaining their original configuration.
Resume and Pause
Teardown any stack that doesn’t need to keep running. All data and configurations will be terminated.
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 having to rebuild the stack.
For this use case, use the snapblocs pause and resume features, instead of the teardown.
Once a stack is in a paused state, all Kubernetes worker nodes will be released (0 worker nodes) except for the control plane. During the paused state, all EC2 nodes will be terminated and no stack components or business applications will be accessible, as those Kubernetes worker pods were terminated. The storage volumes will remain so that no data will be lost during the paused state. When a stack is resumed those volumes will be attached to newly created worker nodes (running containers for the application, data, and stack components).