karpenter_disruption_budget_nodes

Description

The karpenter_disruption_budget_nodes parameter sets the maximum number of Karpenter workload nodes that can be disrupted simultaneously during consolidation or drift replacement.

Default Value

The default value is 10%.

Setting the Parameter

$ convox rack params set karpenter_disruption_budget_nodes=3 -r rackName
Updating parameters... OK

Additional Information

• Validation: Must be a node count or a percentage from 0% to 100%, matching the regex ^((100|[0-9]{1,2})%|[0-9]+)$ (e.g., 10%, 3). This matches the Karpenter NodePool validation, so a percentage above 100% is rejected by the CLI instead of failing a Rack update.
• This limits how many nodes Karpenter can drain at once during consolidation and drift reconciliation. It does not limit node expiry: nodes that reach karpenter_node_expiry are removed regardless of the budget.
• This parameter applies to the workload NodePool only. The build NodePool has its own cap, karpenter_build_disruption_budget_nodes.
• To stop disruptions during a recurring window, such as business hours, set karpenter_disruption_block_schedule and karpenter_disruption_block_duration together. They cover the workload, build and custom pools in one setting. Use karpenter_config for a budget list the two parameters cannot express, such as several windows or a per-reason cap.

See Also

• Karpenter for the full Karpenter configuration reference
• karpenter_build_disruption_budget_nodes for the same cap on the build NodePool
• karpenter_node_expiry
• karpenter_consolidation_enabled
• karpenter_disruption_block_schedule for when a recurring no-disruption window opens
• karpenter_disruption_block_duration for how long that window stays open