ezgh lb load-balancers create <name> --subnet <sbn_…> [--ipv4-address <pip_…>] [--ipv6|--no-ipv6] [--description d] [--tag k=v…] [--wait] [flags]Create a load balancer in a subnet: on an allocated public IPv4 address (--ipv4-address), on IPv6, or both. Without --ipv6 or --no-ipv6 it answers on IPv6 too when the subnet has a ::/0 route to the Network Gateway; --ipv6 asks for IPv6 and needs that route, and --no-ipv6 keeps it IPv4 only. Without --ipv4-address it answers on IPv6 only. The subnet needs a route to the Network Gateway for each family it answers on (0.0.0.0/0, and ::/0 for IPv6) and at least 16 free addresses. It takes minutes: --wait waits until it’s active and prints it. Deleting it later leaves the IPv4 address allocated in the project.
Part of ezgh lb load-balancers.
Examples
ezgh lb load-balancers create storefront --subnet sbn_2m9x0a7qpe4k --ipv4-address pip_9d3f1h6j2lnr --wait
ezgh lb load-balancers create internal --subnet sbn_2m9x0a7qpe4k --ipv4-address pip_9d3f1h6j2lnr --no-ipv6
ezgh lb load-balancers create edge --subnet sbn_2m9x0a7qpe4k --ipv6Flags
| Flag | Type | Default | Description |
|---|---|---|---|
--description |
string | what it’s for | |
--ipv4-address |
string | its public IPv4 address (pip_…); leave it out for IPv6 only | |
--ipv6 |
boolean | answer on IPv6 too (the default where the subnet has a ::/0 route to the Network Gateway) | |
--no-ipv6 |
boolean | answer on IPv4 only | |
--subnet |
string | the subnet that holds it (sbn_…) | |
--tag |
string, repeatable | a tag, key=value; repeat for more | |
--wait |
boolean | wait until it’s active, and print it then | |
--wait-timeout |
duration | 10m0s |
how long --wait waits |
This command also takes the global flags.