Skip to content

Commit

Permalink
docs: Update docs for drift (#4375)
Browse files Browse the repository at this point in the history
  • Loading branch information
engedaam authored Aug 4, 2023
1 parent a9f1b1e commit 305edb4
Show file tree
Hide file tree
Showing 4 changed files with 4 additions and 4 deletions.
2 changes: 1 addition & 1 deletion website/content/en/docs/concepts/deprovisioning.md
Original file line number Diff line number Diff line change
Expand Up @@ -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]({{<ref "./deprovisioning/#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" %}}
Expand Down
2 changes: 1 addition & 1 deletion website/content/en/preview/concepts/deprovisioning.md
Original file line number Diff line number Diff line change
Expand Up @@ -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]({{<ref "./deprovisioning/#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" %}}
Expand Down
2 changes: 1 addition & 1 deletion website/content/en/v0.28/concepts/deprovisioning.md
Original file line number Diff line number Diff line change
Expand Up @@ -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]({{<ref "./deprovisioning/#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" %}}
Expand Down
2 changes: 1 addition & 1 deletion website/content/en/v0.29/concepts/deprovisioning.md
Original file line number Diff line number Diff line change
Expand Up @@ -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]({{<ref "./deprovisioning/#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" %}}
Expand Down

0 comments on commit 305edb4

Please sign in to comment.