Manage Load Balancer

This guide explains how to view, manage, and modify an existing Load Balancer in CloudRaya.

From the Load Balancer's Rule List and Rule Detail pages, you can:

• View configuration and status
• Assign or remove backend Virtual Machines
• Add, edit, or remove load balancer rules
• Update the load balancing algorithm
• Delete a rule, or the Load Balancer itself when its last rule is removed

How a Load Balancer Is Structured

A Load Balancer is bound to one Public IP and one VPC/Subnet, chosen when it's first created.

Inside that, it can contain multiple Rules. Each rule has its own:

• Name
• Load balancing algorithm
• Public Port / Private Port mapping
• Assigned backend Virtual Machines

This means a single Load Balancer (one Public IP) can expose several services at once, for example one rule mapping Public Port 80 to Private Port 80, and another mapping Public Port 443 to Private Port 8443, each forwarding to a different set of VMs. Since CloudRaya's Load Balancer works at Layer 4 (TCP/UDP) and does not inspect application-level data, there's no Layer 7-style routing that can share a single rule across multiple ports, each port needs its own rule.

Public Port and Private Port are independent and do not need to match, the Load Balancer forwards traffic arriving on the Public Port to whatever Private Port the backend VM is actually listening on.

The region picker only shows regions that already have at least one running VM, since a Load Balancer's VPC and available VMs both depend on the selected region.

Accessing Load Balancer Details

To manage a Load Balancer:

1. Open Dashboard → Network → Load Balancer
2. Select a Load Balancer from the list
3. Click View Detail

This opens the Rule List page for that Load Balancer.

View Load Balancer and Rule Details

The Rule List page displays information shared by the whole Load Balancer:

• Location / Cloud Zone
• VPC and Subnet
• Public IP address

Below that, the Rule List table shows every rule on this Load Balancer, along with its Public Port, Private Port, assigned VM count, and Private IP count.

Click the Detail Rule icon on a row to open that rule's Rule Detail page, which repeats the Load Balancer's shared information plus that specific rule's:

• Rule Name
• Load balancing algorithm
• Public Port / Private Port
• Assigned VM List (VM name and Private IP)

This information helps you verify that the Load Balancer and each of its rules are correctly configured and operating as expected.

Assign or Remove Backend Virtual Machines

Backend Virtual Machines receive traffic forwarded by the Load Balancer.

Assign Virtual Machines

To assign backend VMs:

1. Open the Rule Detail page for the rule you want to assign VMs to
2. Click Assign VM
3. Select one or more Virtual Machines from the list
4. Click Assign

Notes:

• Only VMs within the same VPC and subnet can be assigned
• VMs must be in a running state
• Traffic starts flowing only after at least one VM is assigned

If a VM has more than one Private IP, each Private IP appears as its own selectable row when assigning, and each can be assigned or removed independently.

Remove Virtual Machines

To stop forwarding traffic to a VM:

1. Open the Rule Detail page
2. Locate the assigned VM in the Assigned VM List
3. Click the unlink icon next to the Private IP you want to remove

Removing a VM (or one of its Private IPs):

• Stops traffic forwarding for that Private IP
• Does not delete the VM
• Does not affect other backend VMs or other rules

Add Load Balancer Rule

Load Balancer rules define how incoming traffic is forwarded from the Public IP to backend Virtual Machines.

You can add multiple rules to a single Load Balancer to expose different services or ports.

When to Add a Rule

You may need to add a new rule when:

• Exposing a new service on a different port
• Adding HTTPS alongside HTTP
• Running multiple applications behind the same Load Balancer
• Forwarding traffic to a different backend port

Steps to Add a Rule

1. Open the Rule List page
2. Click Add Rule

The new rule reuses the Load Balancer's existing Region, Public IP, VPC, and Subnet, these cannot be changed per rule. Only the Rule Name, Algorithm, and Port Mapping are configured per rule.

Configure Rule Settings

When adding a rule, configure the following:

Rule Name

A descriptive name for the rule.

Examples:

• http-rule
• app-8080

Load Balancing Algorithm

Choose how traffic is distributed:

• Round Robin
• Least Connection
• Source

📄 See: Load Balancer Algorithms for behavior details and use cases.

Public Port

The port exposed on the Load Balancer’s Public IP.

Examples:

• 80
• 443
• 8080

Private Port

The destination port on backend Virtual Machines.

This must match the port where the application is listening.

Examples:

• 80
• 8080
• 3000

Backend Virtual Machines

Select one or more backend VMs.

Notes:

• Only VMs in the same VPC and subnet are available
• VMs must be running
• Multiple VMs can be assigned to one rule

Save the Rule

1. Review the configuration
2. Click Save

The rule becomes active immediately and applies to new incoming connections.

Edit a Rule

Editing a rule only lets you change its:

• Name
• Load balancing algorithm

Public Port and Private Port cannot be changed after a rule is created. To change ports, delete the rule and create a new one instead. Assigned backend VMs are also managed separately through Assign VM, not through Edit.

Editing a Rule

1. Open the Rule List or Rule Detail page
2. Click Edit
3. Update the Name and/or Algorithm
4. Click Update

Changes apply to new incoming connections immediately.

Supported algorithms:

• Round Robin
• Least Connection
• Source

📄 See: Load Balancer Algorithms for behavior details and use cases.

Delete a Rule (and the Load Balancer)

There is no separate "delete the whole Load Balancer" action. Deleting is done per rule.

Steps

1. Open the Rule List page (or a specific Rule Detail page)
2. Click Delete on the rule
3. Confirm the action

What Happens When You Delete a Rule

• If other rules still exist on that Load Balancer, only the deleted rule is removed. Traffic for its port stops, but the Load Balancer, its Public IP, and its other rules keep running.
• If it's the last remaining rule, deleting it removes the entire Load Balancer along with it.

What Happens to the Public IP When the Load Balancer Is Removed

When the last rule (and therefore the Load Balancer) is deleted, the associated Public IP is automatically retained, not released.

Because it's retained automatically, it keeps counting toward your quota and continues to be billed until you release it manually from Dashboard → Public IP Address.

📄 See: Release or Retain a Public IP

Billing and Resource Behavior

• Load Balancer service itself does not incur usage charges
• Billing applies only to:
  • Associated Public IP
  • Backend resources (VMs, storage, etc.)
• Removing all rules (and therefore the Load Balancer) does not automatically stop Public IP billing unless the IP is released afterward

Common Management Scenarios

You may manage a Load Balancer when:

• Adding or removing backend VMs
• Adjusting ports or traffic flow
• Changing the load balancing algorithm
• Migrating applications
• Cleaning up unused resources

Related Pages

📄 Load Balancer Overview

📄 Create a Load Balancer

📄 Load Balancer Algorithms

📄 Public IP Address

📄 Release or Retain a Public IP