Rebalance workloads that use local-path Persistent Volumes.
WARNING: THIS WILL RESULT IN DATA LOSS.

Pods spawned by Jobs or CronJobs will not prevent the Rebalancer from deleting a node on which they run.
WARNING: When true, pods spawned by Jobs or CronJobs will be terminated if the Rebalancer picks a node that runs them.
As such, they are likely to lose their progress.

Pods that are marked with "removal disabled" will not prevent the Rebalancer from deleting a node on which they run.
WARNING: When true, such pods will be evicted and disrupted.

Pods that don't have a controller (bare pods) will not prevent the Rebalancer from deleting a node on which they run.
WARNING: When true, such pods might not restart, since they have no controller to do it.

Ignore instance criteria constraints from node pools during rebalancing.
When true, removes requirements that constrain instance types by name patterns
(instance-category, instance-family, instance-generation, instance-size, instance-cpu, instance-memory).
This allows the rebalancer to select from a broader range of instance types.

Use aggressive eviction of NodeClaims which could block rebalancing plan execution
When true, NodeClaims and pods on them will be forcefully deleted after a default or specified
time interval has passed

Ignore pods blocked by PodDisruptionBudgets with 0 disruptions allowed.
WARNING: May violate PDB guarantees during eviction.

Ignore NodePool disruption budgets that allow 0 disruptions.
When true, overrides zero-disruption NodePool budgets with the default 10% safety budget
so rebalancing can proceed.
WARNING: May violate NodePool disruption budget guarantees.

Nodes that are marked with "removal disabled" or "do-not-disrupt" annotations/labels
will not prevent the Rebalancer from deleting them.
WARNING: When true, such nodes will be disrupted despite their protection annotations.

When true, bypasses the Karpenter Consolidatable condition check during node
candidate selection. Nodes that Karpenter has not yet marked as consolidatable
(e.g. the ConsolidateAfter time window has not elapsed) will still be considered
for rebalancing.
WARNING: May disrupt nodes before Karpenter's own consolidation timing.