# Step 4: Create a Load Balancer Now that your DuploCloud Service is running, you have a mechanism to expose the containers and images in which your application resides. But because your containers are running inside a private network, you also need a load balancer to listen on the correct ports in order to access the application. In this step, we add a Load Balancer Listener to complete this network configuration. *Estimated time to complete Step 4: 10 minutes.* ## Prerequisites Before creating a Load Balancer, verify that you accomplished the tasks in the previous tutorial steps. Using the DuploCloud Portal, confirm that: * An [Infrastructure and Plan](https://docs.duplocloud.com/docs/automation-platform/overview-1/quick-start/step-1-infrastructure) exist, both with the name you created. * The Infrastructure you created has [GKE Enabled](https://docs.duplocloud.com/docs/automation-platform/overview-1/quick-start/step-1-infrastructure). * A [Tenant](https://docs.duplocloud.com/docs/automation-platform/overview-2/quick-start/step-2-tenant) with the name you chose has been created. * A [Service](https://docs.duplocloud.com/docs/automation-platform/overview-1/quick-start/create-a-service-with-gke-autopilot/step-3-create-app-via-k8s) with the name you chose has been created. ### Select the Tenant you created In the **Tenant** list box, on the upper-left side of the DuploCloud Portal, select the Tenant that you created. ## Creating a Load Balancer All containers are running inside a private network and cannot be accessed from an external network. To do so one can create a load balancer. 1. In the DuploCloud Portal, navigate to **Kubernetes** -> **Services**. The **Services** page displays. 2. From the **Name** column, click on the name of your **Service** 3. Click the **Load Balancers** tab. 4. Click the **Configure Load Balancer** link. The **Add Load Balancer Listener** pane displays.

5. From the **Type** list box, select **Application LB**. 6. In the **Container Port** field, enter **80**. This is the configured port on which the application inside the Docker Container Image is running. 7. In the **External Port** field, enter **80**. This is the port through which users will access the web application. 8. From the **Visibility** list box, select **Public**. 9. From the **Application Mode** list box, select **Docker Mode**. 10. In the **Health Check** field, enter **`/`** (forward-slash) to indicate that Kubernetes should check the health of the service at the root of the application. 11. In the **Backend Protocol** list box, select **HTTP**. HTTP is used for this tutorial since we are not setting up SSL certificates. However, using HTTPS to encrypt data between the user and the server when configuring Load Balancers is highly recommended. If you decide to use HTTPS, you must [configure SSL certificates](https://docs.duplocloud.com/docs/automation-platform/overview-1/prerequisites/certificate-for-load-balancer-and-ingress). 12. **Certificates:** You can leave this field empty, as SSL certificates are not necessary for this tutorial. However, we recommend using SSL certificates with Load Balancers to ensure secure HTTPS connections. If you'd like to add SSL certificates for your domain later, follow the instructions [here](https://docs.duplocloud.com/docs/automation-platform/overview-1/prerequisites/certificate-for-load-balancer-and-ingress). 13. Click **Add**. The Load Balancer is created and initialized. In approximately 2-3 minutes you will see the load balancer details available in the portal. When the Load Balancer is ready for use the **LB Status** card displays **Ready**. ## Checking your work 1. From the DuploCloud portal, navigate to **Kubernetes** -> **Services**. 2. Click on the name of your **Service**. 3. Verify that the Load Balancer has a status of **Ready** on the **LB Status** card.