Skip to content

docs: document strict spot capacity behavior #246

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
mintlify wants to merge 1 commit into
base: main
Choose a base branch
from
Open

docs: document strict spot capacity behavior #246

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
24 changes: 24 additions & 0 deletions cloud-accounts/node-groups.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -130,6 +130,30 @@ Create custom node groups for specialized workloads like GPU processing, high-me

---

## Spot Instances

Spot node groups run exclusively on spot capacity. Porter configures spot node groups with a strict capacity type, meaning they will only provision spot instances and will not fall back to on-demand instances if spot capacity is unavailable.

<Warning>
Because there is no on-demand fallback, applications running on spot node groups must tolerate spot interruptions. Configure proper [health checks](/applications/configure/zero-downtime-deployments#health-checks) and ensure workloads can be safely rescheduled when spot instances are reclaimed.
</Warning>

When to use spot:

- Stateless, fault-tolerant workloads (e.g., batch jobs, background workers)
- Development or staging environments where occasional interruptions are acceptable
- Workloads with sufficient replicas to handle node terminations gracefully

When not to use spot:

- Stateful services without redundancy
- Latency-sensitive workloads that cannot tolerate restarts
- Long-running jobs that cannot checkpoint progress

To run a workload on spot capacity, create a custom node group with the **Fixed Instance Type** option and select a spot-enabled instance type, then [assign your application](#assigning-workloads-to-node-groups) to that node group.

---

## Assigning Workloads to Node Groups

Once your custom node group is created, assign applications to run on it:
Expand Down