Workspace-scoped load balancers

Loopback supports load balancers at two scopes:

• Project-level — shared across the project (see Project resources).
• Workspace-level — this page.

What a workspace load balancer is

A managed load balancer object with:

• Name, IPv4/IPv6 addresses (once provisioned).
• Algorithm — e.g. round robin or least connections.
• Optional DNS hostname integration.
• Usage statistics (daily/total traffic counters in the model).

It may link to a monitoring object for health probes.

Targets and services

Targets point at backend servers (often hosts in the same workspace) with ports and weights.

Services (in the Loopback LB sense) group frontend ports / protocols and tie to targets — analogous to listeners + backend pools in cloud LBs.

Creation flows validate organization/project/workspace alignment and RBAC on:

• project.workspace.load_balancer
• project.workspace.load_balancer.target
• project.workspace.load_balancer.service

Relationship to Kubernetes Service type=LoadBalancer

Kubernetes may create cloud load balancers via CCM. Loopback workspace load balancers are a product object for Loopback-managed edge — both can coexist; do not confuse the two in runbooks.

The Kubernetes API proxy also lists LoadBalancer-type Services for visibility — see Kubernetes user features.

Related reading

• Project load balancers
• Hosts
• Monitoring