Proper revert

aws · Jan 23, 2024 · a80e7f1 · a80e7f1
1 parent 1724fbc
commit a80e7f1
Show file tree

Hide file tree

Showing 2 changed files with 16 additions and 16 deletions.
diff --git a/website/content/en/v0.30/concepts/deprovisioning.md b/website/content/en/v0.30/concepts/deprovisioning.md
@@ -162,12 +162,12 @@ In special cases, drift can correspond to multiple values and must be handled di
 Behavioral Fields are treated as over-arching settings on the NodePool to dictate how Karpenter behaves. These fields don’t correspond to settings on the NodeClaim or instance. They’re set by the user to control Karpenter’s Provisioning and disruption logic. Since these don’t map to a desired state of NodeClaims, __behavioral fields are not considered for Drift__.
 
 __Behavioral Fields__
-- Weight
-- Limits
-- ConsolidationPolicy
-- ConsolidateAfter
-- ExpireAfter
----
+- Weight                      
+- Limits                      
+- ConsolidationPolicy               
+- ConsolidateAfter      
+- ExpireAfter  
+---      
 
 Read the [Drift Design](https://github.com/aws/karpenter-core/blob/main/designs/drift.md) for more.
 
@@ -216,7 +216,7 @@ Voluntary node removal does not include [Interruption]({{<ref "#interruption" >}
 
 ### Node-Level Controls
 
-Nodes can be opted out of consolidation and expiration deprovisioning by setting the annotation `karpenter.sh/do-not-consolidate: "true"` on the node.
+Nodes can be opted out of consolidation deprovisioning by setting the annotation `karpenter.sh/do-not-consolidate: "true"` on the node.
 
 ```yaml
 apiVersion: v1
@@ -228,7 +228,7 @@ metadata:
 
 #### Example: Disable Consolidation on Provisioner
 
-Provisioner `.spec.annotations` allow you to set annotations that will be applied to all nodes launched by this provisioner. By setting the annotation `karpenter.sh/do-not-consolidate: "true"` on the provisioner, you will selectively prevent all nodes launched by this Provisioner from being considered in consolidation or expiration actions.
+Provisioner `.spec.annotations` allow you to set annotations that will be applied to all nodes launched by this provisioner. By setting the annotation `karpenter.sh/do-not-consolidate: "true"` on the provisioner, you will selectively prevent all nodes launched by this Provisioner from being considered in consolidation calculations.
 
 ```yaml
 apiVersion: karpenter.sh/v1alpha5

diff --git a/website/content/en/v0.31/concepts/deprovisioning.md b/website/content/en/v0.31/concepts/deprovisioning.md
@@ -162,12 +162,12 @@ In special cases, drift can correspond to multiple values and must be handled di
 Behavioral Fields are treated as over-arching settings on the NodePool to dictate how Karpenter behaves. These fields don’t correspond to settings on the NodeClaim or instance. They’re set by the user to control Karpenter’s Provisioning and disruption logic. Since these don’t map to a desired state of NodeClaims, __behavioral fields are not considered for Drift__.
 
 __Behavioral Fields__
-- Weight
-- Limits
-- ConsolidationPolicy
-- ConsolidateAfter
-- ExpireAfter
----
+- Weight                      
+- Limits                      
+- ConsolidationPolicy               
+- ConsolidateAfter      
+- ExpireAfter  
+---      
 
 Read the [Drift Design](https://github.com/aws/karpenter-core/blob/main/designs/drift.md) for more.
 
@@ -215,7 +215,7 @@ Voluntary node removal does not include [Interruption]({{<ref "#interruption" >}
 
 ### Node-Level Controls
 
-Nodes can be opted out of consolidation and expiration deprovisioning by setting the annotation `karpenter.sh/do-not-consolidate: "true"` on the node.
+Nodes can be opted out of consolidation deprovisioning by setting the annotation `karpenter.sh/do-not-consolidate: "true"` on the node.
 
 ```yaml
 apiVersion: v1
@@ -227,7 +227,7 @@ metadata:
 
 #### Example: Disable Consolidation on Provisioner
 
-Provisioner `.spec.annotations` allow you to set annotations that will be applied to all nodes launched by this provisioner. By setting the annotation `karpenter.sh/do-not-consolidate: "true"` on the provisioner, you will selectively prevent all nodes launched by this Provisioner from being considered in consolidation or expiration actions.
+Provisioner `.spec.annotations` allow you to set annotations that will be applied to all nodes launched by this provisioner. By setting the annotation `karpenter.sh/do-not-consolidate: "true"` on the provisioner, you will selectively prevent all nodes launched by this Provisioner from being considered in consolidation calculations.
 
 ```yaml
 apiVersion: karpenter.sh/v1alpha5