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
Copy file name to clipboardExpand all lines: website/content/en/v1.0/tasks/managing-amis.md
+22Lines changed: 22 additions & 0 deletions
Original file line number
Diff line number
Diff line change
@@ -158,3 +158,25 @@ In a scenario where a faulty AMI is rolling out and begins causing downtime to y
158
158
159
159
The Karpenter project continues to add features to give you greater control over AMI upgrades on your clusters.
160
160
If you have opinions about features you would like to see to manage AMIs with Karpenter, feel free to enter a Karpenter [New Issue](https://github.com/aws/karpenter-provider-aws/issues/new/choose).
161
+
162
+
### Dynamic Volume Size Calculation
163
+
164
+
The `volumeSize` field in the `EC2NodeClass` now supports dynamic calculation based on the number of CPUs in the node. This allows you to configure EBS volume sizes that scale with the node's CPU count, reducing disk space waste and simplifying configuration.
165
+
166
+
#### Example Configurations
167
+
168
+
- **Static Volume Size:**
169
+
```yaml
170
+
volumeSize: "20Gi"
171
+
```
172
+
This sets a fixed volume size of 20 GiB.
173
+
174
+
- **Dynamic Volume Size:**
175
+
```yaml
176
+
volumeSize: "10Gi * CPU"
177
+
```
178
+
This calculates the volume size as `10Gi` multiplied by the number of CPUs in the node. For example, if the node has 4 CPUs, the volume size will be `40Gi`.
179
+
180
+
#### Benefits
181
+
- Reduces disk space waste by scaling volume sizes dynamically.
182
+
- Simplifies configuration by eliminating the need for multiple `EC2NodeClass` definitions for different node sizes.
0 commit comments