From 49cfb7effd4c9f43fb92415f6bfc358c71def6ff Mon Sep 17 00:00:00 2001 From: jigisha620 Date: Tue, 18 Jun 2024 16:01:06 -0700 Subject: [PATCH] docs: Update disable disruption on nodepool to use budgets --- website/content/en/docs/concepts/disruption.md | 9 ++++----- website/content/en/preview/concepts/disruption.md | 9 ++++----- website/content/en/v0.35/concepts/disruption.md | 9 ++++----- website/content/en/v0.36/concepts/disruption.md | 9 ++++----- website/content/en/v0.37/concepts/disruption.md | 9 ++++----- 5 files changed, 20 insertions(+), 25 deletions(-) diff --git a/website/content/en/docs/concepts/disruption.md b/website/content/en/docs/concepts/disruption.md index aa10df2124f3..001de3a242ff 100644 --- a/website/content/en/docs/concepts/disruption.md +++ b/website/content/en/docs/concepts/disruption.md @@ -291,7 +291,7 @@ metadata: #### Example: Disable Disruption on a NodePool -NodePool `.spec.annotations` allow you to set annotations that will be applied to all nodes launched by this NodePool. By setting the annotation `karpenter.sh/do-not-disrupt: "true"` on the NodePool, you will selectively prevent all nodes launched by this NodePool from being considered in disruption actions. +To disable disruption for all nodes launched by a NodePool, you can configure its `.spec.disruption.budgets`. Setting a budget of zero nodes will prevent any of those nodes from being considered for voluntary disruption. ```yaml apiVersion: karpenter.sh/v1beta1 @@ -299,8 +299,7 @@ kind: NodePool metadata: name: default spec: - template: - metadata: - annotations: # will be applied to all nodes - karpenter.sh/do-not-disrupt: "true" + disruption: + budgets: + - nodes: "0" ``` diff --git a/website/content/en/preview/concepts/disruption.md b/website/content/en/preview/concepts/disruption.md index aa10df2124f3..001de3a242ff 100644 --- a/website/content/en/preview/concepts/disruption.md +++ b/website/content/en/preview/concepts/disruption.md @@ -291,7 +291,7 @@ metadata: #### Example: Disable Disruption on a NodePool -NodePool `.spec.annotations` allow you to set annotations that will be applied to all nodes launched by this NodePool. By setting the annotation `karpenter.sh/do-not-disrupt: "true"` on the NodePool, you will selectively prevent all nodes launched by this NodePool from being considered in disruption actions. +To disable disruption for all nodes launched by a NodePool, you can configure its `.spec.disruption.budgets`. Setting a budget of zero nodes will prevent any of those nodes from being considered for voluntary disruption. ```yaml apiVersion: karpenter.sh/v1beta1 @@ -299,8 +299,7 @@ kind: NodePool metadata: name: default spec: - template: - metadata: - annotations: # will be applied to all nodes - karpenter.sh/do-not-disrupt: "true" + disruption: + budgets: + - nodes: "0" ``` diff --git a/website/content/en/v0.35/concepts/disruption.md b/website/content/en/v0.35/concepts/disruption.md index 44c746da121e..ccefdd91db0a 100644 --- a/website/content/en/v0.35/concepts/disruption.md +++ b/website/content/en/v0.35/concepts/disruption.md @@ -287,7 +287,7 @@ metadata: #### Example: Disable Disruption on a NodePool -NodePool `.spec.annotations` allow you to set annotations that will be applied to all nodes launched by this NodePool. By setting the annotation `karpenter.sh/do-not-disrupt: "true"` on the NodePool, you will selectively prevent all nodes launched by this NodePool from being considered in disruption actions. +To disable disruption for all nodes launched by a NodePool, you can configure its `.spec.disruption.budgets`. Setting a budget of zero nodes will prevent any of those nodes from being considered for voluntary disruption. ```yaml apiVersion: karpenter.sh/v1beta1 @@ -295,8 +295,7 @@ kind: NodePool metadata: name: default spec: - template: - metadata: - annotations: # will be applied to all nodes - karpenter.sh/do-not-disrupt: "true" + disruption: + budgets: + - nodes: "0" ``` diff --git a/website/content/en/v0.36/concepts/disruption.md b/website/content/en/v0.36/concepts/disruption.md index aa10df2124f3..001de3a242ff 100644 --- a/website/content/en/v0.36/concepts/disruption.md +++ b/website/content/en/v0.36/concepts/disruption.md @@ -291,7 +291,7 @@ metadata: #### Example: Disable Disruption on a NodePool -NodePool `.spec.annotations` allow you to set annotations that will be applied to all nodes launched by this NodePool. By setting the annotation `karpenter.sh/do-not-disrupt: "true"` on the NodePool, you will selectively prevent all nodes launched by this NodePool from being considered in disruption actions. +To disable disruption for all nodes launched by a NodePool, you can configure its `.spec.disruption.budgets`. Setting a budget of zero nodes will prevent any of those nodes from being considered for voluntary disruption. ```yaml apiVersion: karpenter.sh/v1beta1 @@ -299,8 +299,7 @@ kind: NodePool metadata: name: default spec: - template: - metadata: - annotations: # will be applied to all nodes - karpenter.sh/do-not-disrupt: "true" + disruption: + budgets: + - nodes: "0" ``` diff --git a/website/content/en/v0.37/concepts/disruption.md b/website/content/en/v0.37/concepts/disruption.md index aa10df2124f3..001de3a242ff 100644 --- a/website/content/en/v0.37/concepts/disruption.md +++ b/website/content/en/v0.37/concepts/disruption.md @@ -291,7 +291,7 @@ metadata: #### Example: Disable Disruption on a NodePool -NodePool `.spec.annotations` allow you to set annotations that will be applied to all nodes launched by this NodePool. By setting the annotation `karpenter.sh/do-not-disrupt: "true"` on the NodePool, you will selectively prevent all nodes launched by this NodePool from being considered in disruption actions. +To disable disruption for all nodes launched by a NodePool, you can configure its `.spec.disruption.budgets`. Setting a budget of zero nodes will prevent any of those nodes from being considered for voluntary disruption. ```yaml apiVersion: karpenter.sh/v1beta1 @@ -299,8 +299,7 @@ kind: NodePool metadata: name: default spec: - template: - metadata: - annotations: # will be applied to all nodes - karpenter.sh/do-not-disrupt: "true" + disruption: + budgets: + - nodes: "0" ```