Load Balancers
Add and configure Load Balancers with DuploCloud Azure
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.
Creating an AKS Ingress
If you need to create an Ingress Load Balancer, refer to the AKS Ingress page in the DuploCloud Kubernetes User Guide.
DuploCloud allows no more than one (0 or 1) Load Balancer per DuploCloud Service.
Add a Load Balancer Listener
Add a load balancer listener that uses the Kubernetes NodePort (K8S NodePort).
Several Load Balancers are available for Azure. See the Azure Documentation for a comparison of each option.
Application LB (Standard load balancer)
Shared App Gateway
Classic (Basic load balancer)
Health Check - Selecting this load balancer allows the Application LB (Standard load balancer) to use Kubernetes Health Check to determine whether your service is running properly.
Before you begin
You must create Services before adding load balancers and listeners. In this example, we name these services s1-alb and s4-nlb, respectively.
Adding a Load Balancer Listener
In the DuploCloud Portal, navigate DevOps -> Containers -> AKS/Native.
On the Services page, select the Service name in the Name column.
Click the Load Balancers tab.
Click Configure Load Balancer. The Add Load Balancer Listener pane appears.
Select a type (such as K8S Node Port) in the Select Type field.
Add the Kubernetes Health Check URL for this container in the Health Check field.
Complete the other fields in the Add Load Balancer Listener and click Add.
Configuring a Load Balancer using rules
Rules specify specific configurations for various types of Load Balancers.
See the Ingress use case for an example of how to configure Load Balancers using rules.
Last updated
