Overview
A pool is a collection of backend member instances that receive traffic from a listener. Pools define how traffic is distributed across members (algorithm), whether sessions are sticky (persistence), and which protocol the pool uses internally. Each listener has a default pool; additional pools can be used for L7 policy-based routing.Prerequisites
- An active Xloud account with appropriate permissions
- Access to the Xloud Dashboard (
https://connect.<your-domain>) or CLI configured with credentials - API credentials sourced (
source admin-openrc.sh)
Distribution Algorithms
| Algorithm | Description | Best For |
|---|---|---|
ROUND_ROBIN | Distributes requests evenly across all UP members | Stateless applications with equal capacity members |
LEAST_CONNECTIONS | Sends new requests to the member with fewest active connections | Long-lived connections with variable request duration |
SOURCE_IP | Routes requests from the same client IP to the same member | Stateful applications without cookie-based persistence |
SOURCE_IP_PORT | Routes based on client IP + port combination | Symmetric NAT environments requiring deterministic mapping |
Create a Pool
- Dashboard
- CLI
Navigate to Pools tab
Open your load balancer in Project → Network → Load Balancers and select
the Pools tab. Click Create Pool.
Configure the pool
| Field | Description |
|---|---|
| Name | Pool display name |
| Protocol | Must match or be compatible with the listener protocol |
| Algorithm | Traffic distribution method |
| Session Persistence | Sticky session configuration (optional) |
Add members
After pool creation, select the pool and click the Members sub-tab.
Click Add Member to register backend instances.
| Field | Description |
|---|---|
| IP Address | Backend instance IP |
| Protocol Port | Port your application listens on |
| Weight | Relative traffic weight (default: 1) |
| Monitor Address/Port | Override health check target if different from member address |
Manage Pool Members
- Dashboard
- CLI
Navigate to your pool and click the Members sub-tab. Use Add Member to register
instances and Delete to remove members that are decommissioned.
Session Persistence
Session persistence routes subsequent requests from the same client to the same backend member, enabling stateful applications to work behind the load balancer.- Source IP
Update Pool Settings
Change distribution algorithm
Remove session persistence
Next Steps
Health Monitors
Configure health probes to automatically remove unhealthy members from pools.
Listeners
Configure the listeners that route traffic to your pools.
Create Load Balancer
Full walkthrough for creating a load balancer with pool and health monitor.
Troubleshooting
Resolve member OFFLINE status and pool connectivity issues.