> For the complete documentation index, see [llms.txt](https://docs.duplocloud.com/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.duplocloud.com/docs/marketplace-agents/aws-extension/policy-model/kubernetes/node-groups.md).

# Node Groups

EC2 node groups that provide compute capacity for your EKS cluster.

{% hint style="info" %}
Node Groups are used on **AWS** only. On Oracle Cloud (OCI), the Cluster Baseline creates a default node pool.
{% endhint %}

Node Groups are managed groups of EC2 instances that provide compute capacity for the EKS cluster. Each node group defines the instance type, scaling configuration, and optional taints or labels applied to its nodes.

{% hint style="info" %}
If your Cluster Baseline uses **EKS Auto Mode**, AWS manages compute capacity automatically and node groups are not required.
{% endhint %}

## Spec

| Field             | Description                                                   |
| ----------------- | ------------------------------------------------------------- |
| **Name**          | The name of the node group                                    |
| **Instance Type** | The EC2 instance type for the nodes (e.g. `m5.large`)         |
| **Minimum Nodes** | Minimum number of nodes in the group                          |
| **Desired Nodes** | Target number of nodes                                        |
| **Maximum Nodes** | Maximum number of nodes (for autoscaling)                     |
| **Disk Size**     | Root volume size in GB                                        |
| **Taints**        | Optional Kubernetes taints applied to all nodes in this group |
| **Labels**        | Optional Kubernetes labels applied to all nodes in this group |

## Dependencies

Node Groups require a **Cluster Baseline**.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.duplocloud.com/docs/marketplace-agents/aws-extension/policy-model/kubernetes/node-groups.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
