From 8de0d30f90fda6757d2ed790f5467d54d5042eb2 Mon Sep 17 00:00:00 2001 From: ryan-mist Date: Wed, 8 Apr 2026 09:03:25 -0700 Subject: [PATCH 1/2] docs: limits.nodes support for dynamic NodePools --- website/content/en/docs/concepts/nodepools.md | 5 ++--- website/content/en/preview/concepts/nodepools.md | 5 ++--- website/content/en/v1.11/concepts/nodepools.md | 5 ++--- 3 files changed, 6 insertions(+), 9 deletions(-) diff --git a/website/content/en/docs/concepts/nodepools.md b/website/content/en/docs/concepts/nodepools.md index 5625fa902972..153cbfc7cc83 100644 --- a/website/content/en/docs/concepts/nodepools.md +++ b/website/content/en/docs/concepts/nodepools.md @@ -149,8 +149,7 @@ spec: limits: cpu: "1000" memory: 1000Gi - # For static NodePools, limits.nodes constrains maximum node count during scaling/drift - # Note : Supported only for static NodePools + # limits.nodes constrains maximum node count during scaling/drift nodes: 10 # Priority given to the NodePool when the scheduler considers which NodePool @@ -418,7 +417,7 @@ The NodePool spec includes a limits section (`spec.limits`), which constrains th 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. -**For Static NodePools:** Only `limits.nodes` is supported. This field constrains the maximum number of nodes during scaling operations or drift replacement. Note that `limits.nodes` is support only on static NodePools. +The `limits.nodes` field constrains the maximum number of nodes during scaling operations or drift replacement. ```yaml apiVersion: karpenter.sh/v1 diff --git a/website/content/en/preview/concepts/nodepools.md b/website/content/en/preview/concepts/nodepools.md index 5625fa902972..153cbfc7cc83 100644 --- a/website/content/en/preview/concepts/nodepools.md +++ b/website/content/en/preview/concepts/nodepools.md @@ -149,8 +149,7 @@ spec: limits: cpu: "1000" memory: 1000Gi - # For static NodePools, limits.nodes constrains maximum node count during scaling/drift - # Note : Supported only for static NodePools + # limits.nodes constrains maximum node count during scaling/drift nodes: 10 # Priority given to the NodePool when the scheduler considers which NodePool @@ -418,7 +417,7 @@ The NodePool spec includes a limits section (`spec.limits`), which constrains th 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. -**For Static NodePools:** Only `limits.nodes` is supported. This field constrains the maximum number of nodes during scaling operations or drift replacement. Note that `limits.nodes` is support only on static NodePools. +The `limits.nodes` field constrains the maximum number of nodes during scaling operations or drift replacement. ```yaml apiVersion: karpenter.sh/v1 diff --git a/website/content/en/v1.11/concepts/nodepools.md b/website/content/en/v1.11/concepts/nodepools.md index 5625fa902972..153cbfc7cc83 100644 --- a/website/content/en/v1.11/concepts/nodepools.md +++ b/website/content/en/v1.11/concepts/nodepools.md @@ -149,8 +149,7 @@ spec: limits: cpu: "1000" memory: 1000Gi - # For static NodePools, limits.nodes constrains maximum node count during scaling/drift - # Note : Supported only for static NodePools + # limits.nodes constrains maximum node count during scaling/drift nodes: 10 # Priority given to the NodePool when the scheduler considers which NodePool @@ -418,7 +417,7 @@ The NodePool spec includes a limits section (`spec.limits`), which constrains th 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. -**For Static NodePools:** Only `limits.nodes` is supported. This field constrains the maximum number of nodes during scaling operations or drift replacement. Note that `limits.nodes` is support only on static NodePools. +The `limits.nodes` field constrains the maximum number of nodes during scaling operations or drift replacement. ```yaml apiVersion: karpenter.sh/v1 From 20b4c1c8e43a3bdda373a7a52bbd4008ec904269 Mon Sep 17 00:00:00 2001 From: ryan-mist Date: Wed, 8 Apr 2026 09:11:04 -0700 Subject: [PATCH 2/2] bump go version --- go.mod | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/go.mod b/go.mod index e56e40b37363..198c8e3fabf4 100644 --- a/go.mod +++ b/go.mod @@ -1,6 +1,6 @@ module github.com/aws/karpenter-provider-aws -go 1.26.1 +go 1.26.2 // TODO: migrate tablewriter to v1.0.8 // https://github.com/olekukonko/tablewriter/blob/c64d84b3ecc64a18cfc8ba10cdd8c52cc13a7d23/MIGRATION.md?plain=1#L661