Network & SecurityLoad Balancer

Create a load balancer

Create a load balancer from the portal in a few minutes. Choose the layer and protocol, add one or more backends, and set routing and health-check behavior. Optional settings — sticky sessions, retries, L7 rules, proxy protocol, and access logs — are on the same form.

Before you begin

  • A verified IBEE Solutions organization — creation requires identity verification (Verify your identity)
  • The address and port of at least one backend (a Cloud VM private IP, a hostname, or a service name)

Create a load balancer

1

Open Load Balancers

In the portal sidebar, click Load Balancer under Network, then click Create Load Balancer.

2

Set the general options

FieldDescription
NameUnique per organization — e.g. orders-gateway
LayerL7 for HTTP/HTTPS or L4 for TCP and TLS passthrough
ProtocolL7: HTTPS (default) or HTTP · L4: tcp or tls_passthrough
3

Add backends

Add one row per backend. Click Add backend for more.

FieldDescription
Typeservice, ip, or hostname
TargetThe service name, IP address, or hostname — e.g. orders-service or 10.8.0.12
PortBackend port, 1–65535 (default 8080)
WeightRelative share of traffic (default 100) — a backend with weight 200 receives twice the traffic of one with weight 100
TLSEnable if the load balancer should connect to this backend over TLS
4

Configure routing and health

Select an Algorithm — round_robin (default), least_request, random, or consistent_hash — and a request Timeout in milliseconds (default 30000).

Set the active health check:

FieldDefault
Typehttp (also https, tcp)
Path (http/https only)/health
Interval10000 ms
Timeout2000 ms
Healthy threshold2 consecutive passes
Unhealthy threshold3 consecutive failures
5

Set optional configuration

  • Sticky sessions (L7 only) — route requests with the same header value to the same backend. Set the Sticky header name (default X-User-ID).
  • Proxy protocol — send PROXY protocol v2 to backends so they see the original client IP.
  • Retries — retry failed requests on 5xx, connection reset, or connect failure. Set Attempts (default 3) and Per-retry timeout (default 5000 ms).
  • L7 rules (L7 only) — priority-ordered routing rules. Each rule has a Priority, a Path prefix (e.g. /api), and an optional Header name/value match.
  • Access logs — enable per-request logging.
6

Create

Click Create Load Balancer. You are redirected to the load balancer’s detail page, which shows its status, endpoint host and port, and the endpoint URL to point your clients or DNS at.

Detail page

The detail page shows four sections:

SectionContents
GeneralName, layer, protocol, status, namespace, created/updated timestamps
EndpointHost, port, URL — plus the custom domain and CNAME target if configured
BackendsType, target, port, weight, and TLS for every backend
L7 RulesPriority, path prefix, and header matches (L7 only)

Click Refresh to re-poll status. If provisioning fails, the error message appears at the bottom of the page.

Troubleshooting

“Backend port must be between 1 and 65535” Each backend needs a valid numeric port.

Creation blocked with a verification message Complete identity verification — the create button is disabled until your organization is verified.

Status stays in a provisioning state Click Refresh on the detail page. If an error message appears, fix the reported issue and recreate; otherwise contact support.