Deployment sizes
Deployments can now choose container CPU and memory within the ranges your release declares, and Alien picks the machines. Change a running deployment from your product:
const res = await alien.deployments.updateCompute(deploymentId, {
compute: { containers: { worker: { cpu: 2, memory: "4Gi", volumeSizeGib: 100 } } },
})Initial setup defaults to Automatic machine sizing. The admin can pin a machine type instead, and clearing the pin returns to automatic. Your product can map its own Small, Medium, and Large sizes to these values without naming provider machine types.
On AWS, a pool's machine type can change at runtime to another type with the same CPU architecture. Alien rolls the existing machines over to it.
- Graviton4: c8g machines are in the AWS catalog
- Machine inventory:
alien deployments machines <deployment>lists the hosts on every deployment - Capacity shortages: initial AWS placement retries when a zone runs out of a machine type