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
# The amount of time a Node can live on the cluster before being removed
120
+
# Avoiding long-running Nodes helps to reduce security vulnerabilities as well as to reduce the chance of issues that can plague Nodes with long uptimes such as file fragmentation or memory leaks from system processes
121
+
# You can choose to disable expiration entirely by setting the string value 'Never' here
122
+
expireAfter: Never
101
123
# References the Cloud Provider's NodeClass resource, see your cloud provider specific documentation
102
124
nodeClassRef:
103
125
name: {{ .NodePool.Name }}
@@ -215,22 +237,6 @@ spec:
215
237
#{{ range $az := $azs }}
216
238
- "{{ $az }}"
217
239
#{{ end }}
218
-
# Karpenter provides the ability to specify a few additional Kubelet args.
219
-
# These are all optional and provide support for additional customization and use cases.
220
-
kubelet:
221
-
clusterDNS: [ "10.0.1.100" ]
222
-
cpuCFSQuota: false
223
-
# {{ if ne .Cluster.ConfigItems.karpenter_max_pods_per_node "" }}
# Disruption section which describes the ways in which Karpenter can disrupt and replace Nodes
235
241
# Configuration in this section constrains how aggressive Karpenter can be with performing operations
236
242
# like rolling Nodes due to them hitting their maximum lifetime (expiry) or scaling down nodes to reduce cluster cost
@@ -240,7 +246,7 @@ spec:
240
246
- nodes: "5%"
241
247
- nodes: "10"
242
248
# Describes which types of Nodes Karpenter should consider for consolidation
243
-
# If using 'WhenUnderutilized', Karpenter will consider all nodes for consolidation and attempt to remove or replace Nodes when it discovers that the Node is underutilized and could be changed to reduce cost
249
+
# If using 'WhenEmptyOrUnderutilized', Karpenter will consider all nodes for consolidation and attempt to remove or replace Nodes when it discovers that the Node is underutilized and could be changed to reduce cost
244
250
# If using `WhenEmpty`, Karpenter will only consider nodes for consolidation that contain no workload pods
245
251
#{{ if and (index .NodePool.ConfigItems "consolidation_policy") (eq .NodePool.ConfigItems.consolidation_policy "WhenEmpty") }}
246
252
consolidationPolicy: WhenEmpty
@@ -249,12 +255,8 @@ spec:
249
255
# You can choose to disable consolidation entirely by setting the string value 'Never' here
250
256
consolidateAfter: {{ or (index .NodePool.ConfigItems "consolidate_after") "10m" }}
251
257
#{{ else }}
252
-
consolidationPolicy: WhenUnderutilized
258
+
consolidationPolicy: WhenEmptyOrUnderutilized
253
259
#{{ end }}
254
-
# The amount of time a Node can live on the cluster before being removed
255
-
# Avoiding long-running Nodes helps to reduce security vulnerabilities as well as to reduce the chance of issues that can plague Nodes with long uptimes such as file fragmentation or memory leaks from system processes
256
-
# You can choose to disable expiration entirely by setting the string value 'Never' here
257
-
expireAfter: Never
258
260
# Priority given to the NodePool when the scheduler considers which NodePool
259
261
# to select. Higher weights indicate higher priority when comparing NodePools.
260
262
# Specifying no weight is equivalent to specifying a weight of 0.
0 commit comments