From 172b5ef8d62e293923aa63bb311a47bbef0a516c Mon Sep 17 00:00:00 2001 From: nikmohan Date: Wed, 10 Jan 2024 11:07:20 -0600 Subject: [PATCH] Docs: Remove additional newline. --- website/content/en/preview/concepts/disruption.md | 1 - 1 file changed, 1 deletion(-) diff --git a/website/content/en/preview/concepts/disruption.md b/website/content/en/preview/concepts/disruption.md index f93a7a95e682..7f6791d2f7c8 100644 --- a/website/content/en/preview/concepts/disruption.md +++ b/website/content/en/preview/concepts/disruption.md @@ -121,7 +121,6 @@ Using preferred anti-affinity and topology spreads can reduce the effectiveness For spot nodes, Karpenter has deletion consolidation enabled by default. It will replace a spot node with a cheaper spot node for both single and multi-node consolidation only if the feature flag `SpotToSpotConsolidation` is enabled. Cheaper spot instance types are selected with the `price-capacity-optimized` strategy and often the cheapest spot instance type is not launched due to the likelihood of interruption. Karpenter would replace consolidation for single-node consolidation only if there are more than 15 potential replacement spot instance types. This threshold ensures that we have enough instance diversity that it's very unlikely that all instances that we select will have high interruption. To enable the spotToSpotConsolidation feature flag, refer to the [Feature Gates]({{}}). - {{% /alert %}} ### Drift