Skip to content

docs: limits.nodes support for dynamic NodePools #9062

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
ryan-mist merged 2 commits into from
Apr 8, 2026
Merged

docs: limits.nodes support for dynamic NodePools #9062

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
8de0d30
docs: limits.nodes support for dynamic NodePools
ryan-mist Apr 8, 2026
20b4c1c
bump go version
ryan-mist Apr 8, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion go.mod
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -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
Expand Down
5 changes: 2 additions & 3 deletions website/content/en/docs/concepts/nodepools.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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
Expand Down Expand Up @@ -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
Expand Down
5 changes: 2 additions & 3 deletions website/content/en/preview/concepts/nodepools.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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
Expand Down Expand Up @@ -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
Expand Down
5 changes: 2 additions & 3 deletions website/content/en/v1.11/concepts/nodepools.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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
Expand Down Expand Up @@ -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
Expand Down
Loading