Creates a NodeBalancer in the requested Region. Only available in regions with "NodeBalancers" in their capabilities.
NodeBalancers are available in premium and basic versions. The following table compares these options. Use this information to help determine which type best meets your application’s requirements for performance, scalability, and protocol support.
NodeBalancers comparison
| Feature | Basic (common) | Premium (premium) |
|---|---|---|
| Load balancing type | Connection termination | Connection termination |
| Maximum inbound network bandwidth | 10 Gbps | 10 Gbps |
| Maximum backend nodes per configuration | 1,000 | 2,000 |
| Concurrent connections (TCP) | 10,000 | 100,000 |
| Infrastructure and performance | Shared, may experience resource contention | Dedicated for consistent, predictable capacity |
| Backend connectivity | Private IPv4 (legacy), VPC (vpc), Public IPv6 (ipv6) | VPC (vpc), Public IPv6 (ipv6) |
| Frontend connectivity | IPv4, IPv6 | IPv4, IPv6 |
| Protocols | TCP, HTTP, HTTPS (1.1) | TCP, HTTP, HTTPS (1.1) |
NodeBalancers require a port config with at least one backend node to start serving requests.
When using the Linode CLI to create a NodeBalancer, first create a NodeBalancer without any configs. Then, create configs and nodes for that NodeBalancer with the respective Create a config and Create a node operations.
After creating a NodeBalancer, account administrators can add a lock to prevent accidental NodeBalancer deletion by using the Create a resource lock operation.
Permissions and scopes
To call this operation, you need the following:
-
Identity and access permissions. Your user needs a role with these permissions assigned. Learn more.
- Permissions:
create_nodebalancer
- Permissions:
-
OAuth scopes. Your user needs these scopes assigned. Learn more.
- Scopes:
nodebalancers:read_write
- Scopes:
CLI
linode-cli nodebalancers create \
--region us-east \
--label balancer12345 \
--backend_connectivity legacy \
--type common \
--ipv4 "192.0.2.141" \
--client_conn_throttle 0