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: docs/warm-up.md
+3-1Lines changed: 3 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -26,6 +26,7 @@ The warm-up size can be configured through the `eni-config` ConfigMap:
26
26
**Important**: The `ip_warm_up_size` is independent of `min_pool_size` and `max_pool_size`. It can be set to a value larger or smaller than the pool size limits.
27
27
28
28
However, setting `ip_warm_up_size` larger than `max_pool_size` is **not recommended** because:
29
+
29
30
- The warm-up process will allocate IPs up to `ip_warm_up_size`
30
31
- After warm-up completes, the pool management and idle IP reclaim policy will release excess IPs to maintain the pool within `min_pool_size` and `max_pool_size` boundaries
31
32
- This results in unnecessary IP allocation and deallocation, wasting resources and API calls
@@ -42,6 +43,7 @@ However, setting `ip_warm_up_size` larger than `max_pool_size` is **not recommen
42
43
```
43
44
44
45
In this example:
46
+
45
47
- On node startup, 15 IPs will be pre-allocated (warm-up)
46
48
- The pool will maintain between 5-20 IPs during normal operation
47
49
- Since `ip_warm_up_size` (15) is within the pool size range (5-20), all pre-allocated IPs will be retained
@@ -58,6 +60,7 @@ In this example:
58
60
```
59
61
60
62
In this example:
63
+
61
64
- On node startup, 20 IPs will be pre-allocated (warm-up)
62
65
- After warm-up completes, 10 IPs will be released because `max_pool_size` is only 10
63
66
- This causes unnecessary IP churn and API calls
@@ -94,4 +97,3 @@ status:
94
97
- Warm-up only runs once per node lifecycle (when the node first joins the cluster)
95
98
- If a node already has warm-up status initialized, changing `ip_warm_up_size` will not affect the ongoing warm-up
96
99
- Warm-up progress is tracked independently of actual IP usage, ensuring consistent behavior even if IPs are allocated/deallocated during warm-up
0 commit comments