> 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/load-balancers.md).

# Load Balancers

Load Balancers are essential when running a service. They expose the containers and images in which your application resides. When your containers are run inside a private network, you need a load balancer to listen on the correct ports to access the application. DuploCloud integrates seamlessly with Azure Load Balancers to expose Kubernetes services or Docker containers.

{% hint style="info" %}
DuploCloud allows no more than one (1) Load Balancer per DuploCloud Service.
{% endhint %}

## **Prerequisites**

Before adding a Load Balancer, you need to create the necessary services:

* **For Kubernetes**: See the DuploCloud documentation for [creating an AKS Service](/docs/automation-platform/overview-2/azure-services/containers-and-services/aks-containers-and-services.md#creating-a-duplocloud-aks-service).
* **For Docker**: Ensure Docker containers are set up and accessible within your infrastructure. For detailed instructions, see the [DuploCloud documentation](/docs/automation-platform/overview-2/azure-services/docker-web-application.md#id-2-toc-title).

To create a **Shared Application Gateway** Load Balancer, refer to the [Shared Application Gateway](/docs/automation-platform/kubernetes-overview/ingress-loadbalancer/aks-ingress.md) documentation

## Adding a Load Balancer

1. In the DuploCloud Portal, navigate to:
   * **Kubernetes** → **Services** for Kubernetes deployments, or
   * **Docker** → **Services** for Docker deployments.
2. On the **Services** page, select the Service name in the **Name** column.
3. Click the **Load Balancers** tab.
4. Click **Configure Load Balancer**. The **Add Load Balancer Listener** pane appears.<br>

   <div align="left"><figure><img src="/files/JTaX4drkE8jIROBocSBq" alt="" width="305"><figcaption><p>The <strong>Add Load Balancer Listener</strong> pane</p></figcaption></figure></div>
5. Fill out the required fields based on your configuration needs.
6. Click **Add** to create the Load Balancer.

## Configuring a Load Balancer using rules

Rules define specific configurations for different types of Load Balancers.

For an example of how to configure Load Balancers using rules, see the [Ingress](/docs/automation-platform/kubernetes-overview/ingress-loadbalancer/aks-ingress.md) use case.

## Restricting Open Access to Public Load Balancers

Restrict open access to your public Load Balancers by enforcing controlled access policies.

1. From the DuploCloud Portal, navigate to **Administrator** -> **System Settings**.
2. Select the **System Config** tab and click **Add**. The **Add Config** pane displays.

<div align="left"><figure><img src="/files/pJsvyDxQUGYk9VXM7mhN" alt="" width="364"><figcaption><p>The <strong>Add Config</strong> pane in the DuploCloud Portal</p></figcaption></figure></div>

3. From the **Config Type** list box, select **Flags**.
4. From the **Key** list box, select **Deny Open Access To Public LB**.
5. In the **Value** list box, select **True**.
6. Click **Submit**. Open access to public Load Balancers is restricted.


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.duplocloud.com/docs/automation-platform/overview-2/azure-services/load-balancers.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.