CPU & Memory Formats
Satusky uses Kubernetes resource quantities.
Current deploy behavior
Section titled “Current deploy behavior”| Input | Backend field |
|---|---|
--cpu / app.cpu | CPU request |
--memory / app.memory | Memory request and memory limit |
There is no separate CPU limit flag and no separate memory limit flag today.
Defaults:
| Field | Default |
|---|---|
| CPU | 0.5 |
| Memory | 256Mi |
Accepted examples:
| Value | Meaning |
|---|---|
100m | 0.1 core |
250m | 0.25 core |
0.5 | 0.5 core |
1 | 1 core |
2 | 2 cores |
Memory
Section titled “Memory”Memory values must include a unit. Use Mi or Gi.
| Value | Meaning |
|---|---|
128Mi | 128 mebibytes |
256Mi | 256 mebibytes |
512Mi | 512 mebibytes |
1Gi | 1 gibibyte |
2Gi | 2 gibibytes |
--memory 512 is rejected because Kubernetes would interpret a bare number as bytes.
HPA and VPA
Section titled “HPA and VPA”HPA targets are percentages:
1ctl deploy --hpa --hpa-cpu-target 70 --hpa-memory-target 80VPA bounds use resource quantities:
1ctl deploy --vpa --vpa-mode Off --vpa-min-cpu 100m --vpa-max-cpu 2 --vpa-min-memory 128Mi --vpa-max-memory 2Gi