Manage Load Balancer

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

From the Load Balancer detail page, 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 the Load Balancer when it is no longer needed

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

The Load Balancer detail page provides a centralized view of all settings and actions.

View Load Balancer Details

The detail page displays key information, including:

• Load Balancer Name
• Region / Cloud Zone
• VPC and Subnet
• Public IP address
• Load balancing algorithm
• Port mapping rules
• Assigned backend Virtual Machines
• Current status

This information helps you verify that the Load Balancer is 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 Load Balancer Detail page
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

Remove Virtual Machines

To stop forwarding traffic to a VM:

1. Open the Load Balancer Detail page
2. Locate the assigned VM
3. Click Remove

Removing a VM:

• Stops traffic forwarding to that VM
• Does not delete the VM
• Does not affect other backend VMs

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 Load Balancer Detail page
2. Click Add 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 Rules and Port Mapping

Load Balancer rules define how traffic is forwarded.

You can update existing rules to change:

• Public Port
• Private Port
• Assigned backend VMs
• Load balancing algorithm

Editing a Rule

1. Open the Load Balancer Detail page
2. Select the rule you want to modify
3. Click Edit
4. Update the configuration
5. Save the changes

Changes apply to new incoming connections immediately.

Update Load Balancing Algorithm

You can change the algorithm at any time.

Supported algorithms:

• Round Robin
• Least Connection
• Source

Updating the algorithm:

• Affects new connections
• Does not interrupt existing active connections

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

Delete a Load Balancer

Deleting a Load Balancer permanently removes it.

Steps

1. Open the Load Balancer Detail page
2. Click Delete Load Balancer
3. Confirm the action

What Happens When You Delete a Load Balancer

• The Load Balancer is removed immediately
• Traffic forwarding stops
• Backend Virtual Machines are not deleted
• The associated Public IP may be:
  • Released, or
  • Retained, depending on your selection

📄 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.)
• Deleting a Load Balancer does not automatically stop Public IP billing unless the IP is released

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