From 70d9733f0908e85ac593ff2a9940cb48bf07d5fb Mon Sep 17 00:00:00 2001 From: Vacant2333 Date: Wed, 12 Mar 2025 14:57:23 +0800 Subject: [PATCH] add description when the limits were not set Signed-off-by: Vacant2333 --- website/content/en/docs/concepts/nodepools.md | 4 ++-- website/content/en/preview/concepts/nodepools.md | 4 ++-- website/content/en/v0.32/concepts/nodepools.md | 4 ++-- website/content/en/v1.0/concepts/nodepools.md | 4 ++-- website/content/en/v1.2/concepts/nodepools.md | 4 ++-- website/content/en/v1.3/concepts/nodepools.md | 4 ++-- website/content/en/v1.4/concepts/nodepools.md | 4 ++-- 7 files changed, 14 insertions(+), 14 deletions(-) diff --git a/website/content/en/docs/concepts/nodepools.md b/website/content/en/docs/concepts/nodepools.md index 6ae5e7cff69e..b81ef296812c 100644 --- a/website/content/en/docs/concepts/nodepools.md +++ b/website/content/en/docs/concepts/nodepools.md @@ -368,9 +368,9 @@ Read [Disruption]({{}}) for more. ## spec.limits -The NodePool spec includes a limits section (`spec.limits`), which constrains the maximum amount of resources that the NodePool will manage. +The NodePool spec includes a limits section (`spec.limits`), which constrains the maximum amount of resources that the NodePool can consume. -Karpenter supports limits of any resource type reported by your cloudprovider. It limits instance types when scheduling to those that will not exceed the specified limits. If a limit has been exceeded, nodes provisioning is prevented until some nodes have been terminated. +If the `NodePool.spec.limits` section is unspecified, it means that there is no default limitation on resource allocation. In this case, the maximum resource consumption is governed by the quotas set by your cloud provider. If a limit has been exceeded, nodes provisioning is prevented until some nodes have been terminated. ```yaml apiVersion: karpenter.sh/v1 diff --git a/website/content/en/preview/concepts/nodepools.md b/website/content/en/preview/concepts/nodepools.md index 6ae5e7cff69e..b81ef296812c 100644 --- a/website/content/en/preview/concepts/nodepools.md +++ b/website/content/en/preview/concepts/nodepools.md @@ -368,9 +368,9 @@ Read [Disruption]({{}}) for more. ## spec.limits -The NodePool spec includes a limits section (`spec.limits`), which constrains the maximum amount of resources that the NodePool will manage. +The NodePool spec includes a limits section (`spec.limits`), which constrains the maximum amount of resources that the NodePool can consume. -Karpenter supports limits of any resource type reported by your cloudprovider. It limits instance types when scheduling to those that will not exceed the specified limits. If a limit has been exceeded, nodes provisioning is prevented until some nodes have been terminated. +If the `NodePool.spec.limits` section is unspecified, it means that there is no default limitation on resource allocation. In this case, the maximum resource consumption is governed by the quotas set by your cloud provider. If a limit has been exceeded, nodes provisioning is prevented until some nodes have been terminated. ```yaml apiVersion: karpenter.sh/v1 diff --git a/website/content/en/v0.32/concepts/nodepools.md b/website/content/en/v0.32/concepts/nodepools.md index 6a402e4172e1..5306966b03e3 100644 --- a/website/content/en/v0.32/concepts/nodepools.md +++ b/website/content/en/v0.32/concepts/nodepools.md @@ -403,9 +403,9 @@ You can configure Karpenter to disrupt Nodes through your NodePool in multiple w ## spec.limits -The NodePool spec includes a limits section (`spec.limits`), which constrains the maximum amount of resources that the NodePool will manage. +The NodePool spec includes a limits section (`spec.limits`), which constrains the maximum amount of resources that the NodePool can consume. -Karpenter supports limits of any resource type reported by your cloudprovider. It limits instance types when scheduling to those that will not exceed the specified limits. If a limit has been exceeded, nodes provisioning is prevented until some nodes have been terminated. +If the `NodePool.spec.limits` section is unspecified, it means that there is no default limitation on resource allocation. In this case, the maximum resource consumption is governed by the quotas set by your cloud provider. If a limit has been exceeded, nodes provisioning is prevented until some nodes have been terminated. ```yaml apiVersion: karpenter.sh/v1beta1 diff --git a/website/content/en/v1.0/concepts/nodepools.md b/website/content/en/v1.0/concepts/nodepools.md index b9550d2b9788..886e4b93df43 100644 --- a/website/content/en/v1.0/concepts/nodepools.md +++ b/website/content/en/v1.0/concepts/nodepools.md @@ -367,9 +367,9 @@ Read [Disruption]({{}}) for more. ## spec.limits -The NodePool spec includes a limits section (`spec.limits`), which constrains the maximum amount of resources that the NodePool will manage. +The NodePool spec includes a limits section (`spec.limits`), which constrains the maximum amount of resources that the NodePool can consume. -Karpenter supports limits of any resource type reported by your cloudprovider. It limits instance types when scheduling to those that will not exceed the specified limits. If a limit has been exceeded, nodes provisioning is prevented until some nodes have been terminated. +If the `NodePool.spec.limits` section is unspecified, it means that there is no default limitation on resource allocation. In this case, the maximum resource consumption is governed by the quotas set by your cloud provider. If a limit has been exceeded, nodes provisioning is prevented until some nodes have been terminated. ```yaml apiVersion: karpenter.sh/v1 diff --git a/website/content/en/v1.2/concepts/nodepools.md b/website/content/en/v1.2/concepts/nodepools.md index a4a681e051e5..e5b53e681732 100644 --- a/website/content/en/v1.2/concepts/nodepools.md +++ b/website/content/en/v1.2/concepts/nodepools.md @@ -367,9 +367,9 @@ Read [Disruption]({{}}) for more. ## spec.limits -The NodePool spec includes a limits section (`spec.limits`), which constrains the maximum amount of resources that the NodePool will manage. +The NodePool spec includes a limits section (`spec.limits`), which constrains the maximum amount of resources that the NodePool can consume. -Karpenter supports limits of any resource type reported by your cloudprovider. It limits instance types when scheduling to those that will not exceed the specified limits. If a limit has been exceeded, nodes provisioning is prevented until some nodes have been terminated. +If the `NodePool.spec.limits` section is unspecified, it means that there is no default limitation on resource allocation. In this case, the maximum resource consumption is governed by the quotas set by your cloud provider. If a limit has been exceeded, nodes provisioning is prevented until some nodes have been terminated. ```yaml apiVersion: karpenter.sh/v1 diff --git a/website/content/en/v1.3/concepts/nodepools.md b/website/content/en/v1.3/concepts/nodepools.md index 6ae5e7cff69e..b81ef296812c 100644 --- a/website/content/en/v1.3/concepts/nodepools.md +++ b/website/content/en/v1.3/concepts/nodepools.md @@ -368,9 +368,9 @@ Read [Disruption]({{}}) for more. ## spec.limits -The NodePool spec includes a limits section (`spec.limits`), which constrains the maximum amount of resources that the NodePool will manage. +The NodePool spec includes a limits section (`spec.limits`), which constrains the maximum amount of resources that the NodePool can consume. -Karpenter supports limits of any resource type reported by your cloudprovider. It limits instance types when scheduling to those that will not exceed the specified limits. If a limit has been exceeded, nodes provisioning is prevented until some nodes have been terminated. +If the `NodePool.spec.limits` section is unspecified, it means that there is no default limitation on resource allocation. In this case, the maximum resource consumption is governed by the quotas set by your cloud provider. If a limit has been exceeded, nodes provisioning is prevented until some nodes have been terminated. ```yaml apiVersion: karpenter.sh/v1 diff --git a/website/content/en/v1.4/concepts/nodepools.md b/website/content/en/v1.4/concepts/nodepools.md index 6ae5e7cff69e..b81ef296812c 100644 --- a/website/content/en/v1.4/concepts/nodepools.md +++ b/website/content/en/v1.4/concepts/nodepools.md @@ -368,9 +368,9 @@ Read [Disruption]({{}}) for more. ## spec.limits -The NodePool spec includes a limits section (`spec.limits`), which constrains the maximum amount of resources that the NodePool will manage. +The NodePool spec includes a limits section (`spec.limits`), which constrains the maximum amount of resources that the NodePool can consume. -Karpenter supports limits of any resource type reported by your cloudprovider. It limits instance types when scheduling to those that will not exceed the specified limits. If a limit has been exceeded, nodes provisioning is prevented until some nodes have been terminated. +If the `NodePool.spec.limits` section is unspecified, it means that there is no default limitation on resource allocation. In this case, the maximum resource consumption is governed by the quotas set by your cloud provider. If a limit has been exceeded, nodes provisioning is prevented until some nodes have been terminated. ```yaml apiVersion: karpenter.sh/v1