You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Presets follow a cloud-style `<series>.<size>` naming convention. Five series cover the full CPU-to-memory ratio range, and each series ships eight sizes (`nano` through `4xlarge`):
Memory follows from the series ratio. For example, `t1.small` is 1 CPU / 512Mi, `c1.small` is 1 CPU / 1Gi, `s1.small` is 1 CPU / 2Gi, `u1.small` is 1 CPU / 4Gi, and `m1.small` is 1 CPU / 8Gi. Ephemeral storage is 2Gi for every preset.
49
63
50
64
In CPU, the `m` unit is 1/1000th of a full CPU time.
51
65
66
+
#### Watch out: legacy and instance-type `medium` differ
67
+
68
+
The legacy flat preset `medium` had **1 CPU / 1Gi**. The new `*.medium` sizes have **2 CPU**. The names overlap but the resources do not. The legacy table below stays correct — `medium → c1.small (1 CPU / 1Gi)` — but if you read the instance-type sizing matrix first and pick `c1.medium` "to keep things the same as before", you will double your CPU. When in doubt, consult the legacy-to-instance-type mapping below.
69
+
70
+
#### Legacy flat preset names (deprecated)
71
+
72
+
The seven short names that existed before the instance-type rename remain accepted as backward-compatibility aliases. They render exactly the CPU and memory they did before — so an existing HelmRelease or app CR continues to behave identically. The 1:1 mapping is:
73
+
74
+
| Legacy | CPU | Memory | Instance-type equivalent |
Legacy names are scheduled for removal in a future Cozystack release; new manifests should use the instance-type form. The Cozystack API server logs a deprecation warning whenever an app CR carries a legacy value, naming the suggested replacement.
85
+
86
+
A platform upgrade runs a one-shot migration (Migration 39) that walks every `HelmRelease.spec.values` and every app CR under `apps.cozystack.io/v1alpha1` and rewrites legacy values to their instance-type equivalents in place. The conversion is idempotent, best-effort, and never changes CPU or memory.
87
+
52
88
Cozystack presets are defined in an internal library
[`cozy-lib`](https://github.com/cozystack/cozystack/tree/main/packages/library/cozy-lib). The canonical reference, including the full size matrix and migration table, lives in [`docs/operations/resource-presets.md`](https://github.com/cozystack/cozystack/blob/main/docs/operations/resource-presets.md).
54
90
55
91
56
92
### Defining Resources Explicitly
@@ -66,7 +102,7 @@ resources:
66
102
memory: 2Gi
67
103
```
68
104
69
-
If both `resources` and `resourcesPreset` are defined, `resource` is used and `resourcsePreset` is ignored.
105
+
If both `resources` and `resourcesPreset` are defined, `resources` is used and `resourcesPreset` is ignored.
70
106
71
107
72
108
## Resource Requests and Limits
@@ -133,27 +169,31 @@ resources:
133
169
134
170
### Example 1, default setting: `cpu-allocation-ratio: 10`
135
171
172
+
Preset CPU shown for the `t1` series (the legacy `nano … 2xlarge` aliases use the same CPU values; other series share the same `cpu` column per size, so a `c1.small`, `s1.small`, `u1.small`, or `m1.small` each have `cpu: 1` too).
173
+
136
174
| Preset name | `resources.cpu` | actual CPU request | actual CPU limit |
0 commit comments