CPU & Memory Formats

SatuSky applies resource settings per replica. Set them in satusky.toml or with 1ctl deploy flags.

Current deploy behavior

Setting	CLI flag	Default	Meaning
CPU request	--cpu-request	250m	Guaranteed CPU reservation
CPU limit	--cpu-limit	1	Maximum CPU burst
Memory	--memory	256Mi	Memory request and limit

--cpu remains as a deprecated alias for --cpu-limit. New scripts and manifests should use cpu_request and cpu_limit explicitly.

[app]
cpu_request = "250m"
cpu_limit = "1"
memory = "256Mi"

CPU

Kubernetes CPU values are either cores or millicores:

Value	Equivalent
100m	0.1 CPU
250m	0.25 CPU
1	1 CPU
2	2 CPUs

Keep the request at or below the limit. A larger request reserves more capacity and changes the utilization denominator used by HPA.

Memory

Memory values must include a binary unit such as Mi or Gi:

Value	Meaning
128Mi	128 mebibytes
512Mi	512 mebibytes
2Gi	2 gibibytes

Bare values such as --memory 512 are rejected because they are ambiguous and Kubernetes would interpret them as bytes.

HPA and VPA

HPA utilization percentages are calculated against resource requests:

1ctl deploy --hpa --hpa-cpu-target 70 --hpa-memory-target 80

VPA recommendation bounds use the same CPU and memory formats:

1ctl deploy --vpa --vpa-mode Off \
  --vpa-min-cpu 100m --vpa-max-cpu 2 \
  --vpa-min-memory 128Mi --vpa-max-memory 2Gi

Use VPA mode Off when you want recommendations without automatic resource changes.