erun resize

Change a runtime pod's CPU/memory limits and roll it out — without re-running erun init to change two numbers.

Synopsis

erun resize [--tenant <t>] [--environment <e>] --cpu <cpu> --memory <memory> [flags]
erun resize [--tenant <t>] [--environment <e>] --apply-recommendation [flags]

What it does

Pass --cpu and/or --memory explicitly, or --apply-recommendation to size the environment from its own standing sizing recommendation instead of retyping a value ERun already computed. A resize whose resolved size already matches the current one is a no-op that says so — it does not roll the pod for nothing.

erun resize --tenant my-tenant --environment dev --cpu 6 --memory 12Gi
erun resize --tenant my-tenant --environment dev --apply-recommendation
erun resize --tenant my-tenant --environment dev --apply-recommendation --dry-run

--apply-recommendation needs usage history retained inside the environment's own runtime pod, so run it there (over SSH, or through the environment's own MCP resize tool) — a host-side laptop invocation has nothing to read and refuses rather than guessing.

This moves the runtime container's own limits: the throttle/OOM ceiling, and the amount it draws from the namespace's resource quota. It does not change what the Kubernetes scheduler reserves for the pod (a small fixed request, independent of this setting), it does not resize the erun-dind sidecar, and it does not touch any PVC — disk sizing is not part of this command.

Not while someone else is using it

A resize restarts the runtime pod, which would kill any live session inside it — an agent mid-build, a deploy in flight. Before rolling the pod, resize checks the environment's activity leases and refuses, naming who holds it, if the environment is not idle:

resize refused: this environment is held by orchestrator eng-42, user [email protected] (lease "exec_job_attach") — a resize restarts the runtime pod and would interrupt that work; pass the override to resize anyway, or wait until it finishes

Pass --override-lease to roll it anyway. The override is recorded alongside the resize's own lease.

Flags

Flag	Description
--tenant, --environment	Target a specific tenant/environment; default to the current scope.
--cpu <cpu>	Explicit CPU limit (Kubernetes quantity, e.g. 6). Omit to leave CPU unchanged unless --apply-recommendation.
--memory <memory>	Explicit memory limit (Kubernetes quantity, e.g. 12Gi). Omit to leave memory unchanged unless --apply-recommendation.
--apply-recommendation	Size from the environment's own standing sizing recommendation instead of --cpu/--memory.
--override-lease	Roll the pod even though the environment is currently held by another worker.
--orchestrator <id>	The calling orchestrator's own id, recorded on the resize's lease and on the override, if one was needed.
--dry-run	Resolve and print the plan (current → target per resource, held leases, whether an override was needed) without changing anything.
--output json	Emit the full result as JSON.

The full JSON shape and every refusal are specified in Agent reference · erun resize.

From the desktop

The Manage dialog → Runtime tab's sizing recommendation carries a Resize to this action that runs the same operation as --apply-recommendation, so applying it is one click rather than retyping the suggested numbers into the resource sliders. See Runtime pods · What the environment thinks it should be sized as.

From an MCP-connected orchestrator

The same operation reaches an Agent through the resize MCP tool, scoped to that server's own environment — see MCP overview · resize.

Error behaviour

Failure	Behaviour
Tenant/environment can't be resolved.	Errors before anything is read or changed.
Neither --cpu/--memory nor --apply-recommendation given, or both given.	Errors naming the conflict; nothing is read or changed.
--apply-recommendation with no standing recommendation available (no retained usage history, e.g. run from the host rather than in-pod).	Errors saying so, and suggests explicit --cpu/--memory instead.
The resolved target would exceed the environment's namespace quota once the erun-dind sidecar's own limit is accounted for.	Errors naming the resource, the overage, and how much is actually available.
The environment is held by another worker and --override-lease was not passed.	Refuses, naming every holder.
The resolved target already matches the current recorded size.	No-op: reports "already sized" and does not deploy.