Skip to main content
Change how much capacity your app has: more or fewer machines in the cluster, different machine types, or more copies of a service. Monk does not scale on its own. You ask, review the plan and approve. The orchestrator does restart and reschedule managed workloads within its policies. See Watcher and recovery.

​
Before you start

​
Ask Monk

Add machines to the cluster:
Remove machines:
Change machine size. Add nodes of the new size, move work onto them, then remove the old ones:
Run more copies of a service or give it more resources. These are settings in the MANIFEST. Your coding agent edits it and Monk deploys the change:
Get a recommendation:
Check the valid regions, machine types and GPU types first if you’re not sure:

​
What you review

The plan in the local dashboard shows the machines to add or remove, the services that move, and the estimated cost after the change. Removing a node can move or stop the workloads on it, so check the list. Nothing changes until you approve.

​
What you get

The cluster and services at the new size. Check them:

​
Upgrading Monk on the cluster

Nodes are upgraded one at a time.

​
Next