Skip to main content

Container Instances

The Instances page controls how a container application scales. You pick the machine size, set the instance count range and the autoscaling thresholds, then watch CPU and memory charts for the running service.

Instance settings​

The settings form holds the scaling configuration:

  • Machine is the vCPU and RAM tier each instance runs on. It defaults to 1 vCPU / 2GB RAM. Your project plan limits the list of tiers, so larger sizes appear only when your plan allows them.
  • Minimum Instances and Maximum Instances set the range the service can scale between. They default to 1 and 2. The minimum cannot be higher than the maximum, and your plan caps the highest selectable count.
  • Scale on CPU Utilization is the CPU percentage that triggers autoscaling. It defaults to 60.
  • Cooldown for Scaling Up and Cooldown for Scaling Down are the wait periods in seconds before another scaling step. They default to 200 and 300.

Edit the values and use Save to stage the change. Only the fields you changed are sent. Save is disabled until you make a change, and staged changes are applied through the project deploy flow.

Monitoring​

The Monitoring section charts CPU Utilization and Memory Utilization for the service as percentages over time. The time range control switches the window between 1h, 6h, 12h, 1d, 3d, 7d, and 30d. Compare these charts against your Scale on CPU Utilization threshold to check whether the instance range and machine size fit the load.