> 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/automation-platform/overview-2/azure-services/agent-pool.md). # Agent Pools Meet performance demand in AKS workloads by organizing Azure agents into agent pools When you create agent pools to run Azure Kubernetes (AKS) workloads, you create groups of agents available to a pipeline. When you run the pipeline, the pipeline selects the agent that best meets the performance demands of that pipeline. Autoscaling can be enabled when creating agent pools in the DuploCloud Portal. Each agent pool contains nodes backed by virtual host machines. ## Prerequisites To create an agent pool using availability zones, you must first create a [PostgreSQL Flexible Server subnet](/docs/automation-platform/overview-2/azure-services/databases/postgresql-flexible-server.md#create-a-postgresql-flexible-server-subnet-in-the-infrastructure) in the Infrastructure. For agent pools not using availability zones, skip this step. ## Adding an agent pool Create an Azure agent pool for an existing Host in the DuploCloud Portal. 1. From the DuploCloud Portal, navigate to **Cloud Services** -> **Hosts**. 2. Select the **Azure Agent Pool** tab, and Click **Add**. The **Add Azure Agent Pool** page displays.

The **Add Azure Agent Pool** page in the DuploCloud Portal

1. Provide inputs for the **Id**, **Instance Type**, **Min Capacity**, **Max Capacity**, and **Desired Capacity** fields. 2. Enter allocation tags in the **Allocation Tags** field, if required. 3. Optionally, select one or more availability zones from the **Availability Zones** list box. If you select availability zones, you must create a [PostgreSQL Flexible Server subnet](/docs/automation-platform/overview-2/azure-services/databases/postgresql-flexible-server.md#create-a-postgresql-flexible-server-subnet-in-the-infrastructure) in the Infrastructure before adding your agent pool. 4. Optionally, select **Enable Autoscaling**. 5. Select the **Scale Set** priority: **Regular** creates a regular agent pool node with standard priority and **Spot** creates Spot AKS agent pool nodes. 6. If needed, adjust the number of **Max Pods Per Node** from the default of 30.

7. Click **Add**. It may take some time to create the agent pool. When the agent pool is ready, **Succeeded** displays in the **Status** column.

The **Azure Agent Pool** tab on the **Hosts** page shows the **DLJEGA1** agent pool with **Succeeded** status

8. Optionally, select **Enable Autoscaling**. 9. In the **Scale Set Priority** list box, select **Regular**, or **Spot.** If you selected **Spot**, specify a **Scale Set Eviction Policy**, and **Spot Max Price**. ## Editing an agent pool Edit an agent pool: 1. Select **Cloud Services** -> **Hosts** from the navigation menu. 2. Select the **Azure Agent Pool** tab. The **Azure Agent Pool** page displays. 3. In the **Name** column, select the agent pool that you want to edit. 4. Select the **Actions** menu and choose **Edit**.

The **Azure Agent Pool** page with the **Edit** menu option highlighted

5. In the **Update agent pool capacity** pane, edit the pool configuration. 6. Click **Update**. --- # 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/automation-platform/overview-2/azure-services/agent-pool.md?ask=&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.