From 305edb47349a4ab287bad06f82f735931538448b Mon Sep 17 00:00:00 2001 From: Amanuel Engeda <74629455+engedaam@users.noreply.github.com> Date: Fri, 4 Aug 2023 09:34:20 -0700 Subject: [PATCH] docs: Update docs for drift (#4375) --- website/content/en/docs/concepts/deprovisioning.md | 2 +- website/content/en/preview/concepts/deprovisioning.md | 2 +- website/content/en/v0.28/concepts/deprovisioning.md | 2 +- website/content/en/v0.29/concepts/deprovisioning.md | 2 +- 4 files changed, 4 insertions(+), 4 deletions(-) diff --git a/website/content/en/docs/concepts/deprovisioning.md b/website/content/en/docs/concepts/deprovisioning.md index f35978a20f68..002adb9b383e 100644 --- a/website/content/en/docs/concepts/deprovisioning.md +++ b/website/content/en/docs/concepts/deprovisioning.md @@ -55,7 +55,7 @@ There are both automated and manual ways of deprovisioning nodes provisioned by * **Consolidation**: Karpenter works to actively reduce cluster cost by identifying when: * Nodes can be removed as their workloads will run on other nodes in the cluster. * Nodes can be replaced with cheaper variants due to a change in the workloads. -* **Drift**: Karpenter will annotate nodes as drifted and deprovision nodes that have drifted from their desired specification. Currently, Karpenter will only automatically mark nodes as drifted in the case of a drifted AMI. +* **Drift**: Karpenter will annotate nodes as drifted and deprovision nodes that have drifted from their desired specification. See [Drift]({{}}) to see which fields are considered. * **Interruption**: If enabled, Karpenter will watch for upcoming involuntary interruption events that could affect your nodes (health events, spot interruption, etc.) and will cordon, drain, and terminate the node(s) ahead of the event to reduce workload disruption. {{% alert title="Note" color="primary" %}} diff --git a/website/content/en/preview/concepts/deprovisioning.md b/website/content/en/preview/concepts/deprovisioning.md index d1c23b8dc73e..c9676f21155b 100644 --- a/website/content/en/preview/concepts/deprovisioning.md +++ b/website/content/en/preview/concepts/deprovisioning.md @@ -55,7 +55,7 @@ There are both automated and manual ways of deprovisioning nodes provisioned by * **Consolidation**: Karpenter works to actively reduce cluster cost by identifying when: * Nodes can be removed as their workloads will run on other nodes in the cluster. * Nodes can be replaced with cheaper variants due to a change in the workloads. -* **Drift**: Karpenter will annotate nodes as drifted and deprovision nodes that have drifted from their desired specification. Currently, Karpenter will only automatically mark nodes as drifted in the case of a drifted AMI. +* **Drift**: Karpenter will annotate nodes as drifted and deprovision nodes that have drifted from their desired specification. See [Drift]({{}}) to see which fields are considered. * **Interruption**: If enabled, Karpenter will watch for upcoming involuntary interruption events that could affect your nodes (health events, spot interruption, etc.) and will cordon, drain, and terminate the node(s) ahead of the event to reduce workload disruption. {{% alert title="Note" color="primary" %}} diff --git a/website/content/en/v0.28/concepts/deprovisioning.md b/website/content/en/v0.28/concepts/deprovisioning.md index a529f22acfb4..7926981298eb 100644 --- a/website/content/en/v0.28/concepts/deprovisioning.md +++ b/website/content/en/v0.28/concepts/deprovisioning.md @@ -55,7 +55,7 @@ There are both automated and manual ways of deprovisioning nodes provisioned by * **Consolidation**: Karpenter works to actively reduce cluster cost by identifying when: * Nodes can be removed as their workloads will run on other nodes in the cluster. * Nodes can be replaced with cheaper variants due to a change in the workloads. -* **Drift**: Karpenter will annotate nodes as drifted and deprovision nodes that have drifted from their desired specification. Currently, Karpenter will only automatically mark nodes as drifted in the case of a drifted AMI. +* **Drift**: Karpenter will annotate nodes as drifted and deprovision nodes that have drifted from their desired specification. See [Drift]({{}}) to see which fields are considered. * **Interruption**: If enabled, Karpenter will watch for upcoming involuntary interruption events that could affect your nodes (health events, spot interruption, etc.) and will cordon, drain, and terminate the node(s) ahead of the event to reduce workload disruption. {{% alert title="Note" color="primary" %}} diff --git a/website/content/en/v0.29/concepts/deprovisioning.md b/website/content/en/v0.29/concepts/deprovisioning.md index f35978a20f68..002adb9b383e 100644 --- a/website/content/en/v0.29/concepts/deprovisioning.md +++ b/website/content/en/v0.29/concepts/deprovisioning.md @@ -55,7 +55,7 @@ There are both automated and manual ways of deprovisioning nodes provisioned by * **Consolidation**: Karpenter works to actively reduce cluster cost by identifying when: * Nodes can be removed as their workloads will run on other nodes in the cluster. * Nodes can be replaced with cheaper variants due to a change in the workloads. -* **Drift**: Karpenter will annotate nodes as drifted and deprovision nodes that have drifted from their desired specification. Currently, Karpenter will only automatically mark nodes as drifted in the case of a drifted AMI. +* **Drift**: Karpenter will annotate nodes as drifted and deprovision nodes that have drifted from their desired specification. See [Drift]({{}}) to see which fields are considered. * **Interruption**: If enabled, Karpenter will watch for upcoming involuntary interruption events that could affect your nodes (health events, spot interruption, etc.) and will cordon, drain, and terminate the node(s) ahead of the event to reduce workload disruption. {{% alert title="Note" color="primary" %}}