Authorizations
API key for authentication. Make sure to include the word apikey
, followed by a single space and then your token.
Example: apikey 1234$abcdef
Body
Load balancer flavor name
"lb1-1-2"
"lb2-2-2"
Floating IP configuration for assignment
{
"existing_floating_id": "c64e5db1-5f1f-43ec-a8d9-5090df85b82d",
"source": "existing"
}
Load balancer listeners. Maximum 50 per LB (excluding Prometheus endpoint listener).
51
Logging configuration
Load balancer name
"new_load_balancer"
Load balancer name which will be changed by template.
"lb_name_template"
Preferred option to establish connectivity between load balancer and its pools members. L2 provides best performance, L3 provides less IPs usage. It is taking effect only if instance_id
+ ip_address
is provided, not subnet_id
+ ip_address
, because we're considering this as intentional subnet_id
specification.
L2
, L3
Key-value tags to associate with the resource. A tag is a key-value pair that can be associated with a resource, enabling efficient filtering and grouping for better organization and management. Some tags are read-only and cannot be modified by the user. Tags are also integrated with cost reports, allowing cost data to be filtered based on tag keys or values.
IP family for load balancer subnet auto-selection if vip_network_id
is specified
dual
, ipv4
, ipv6
Network ID for load balancer. If not specified, default external network will be used. Mutually exclusive with vip_port_id
"ac307687-31a4-4a11-a949-6bea1b2878f5"
Existing Reserved Fixed IP port ID for load balancer. Mutually exclusive with vip_network_id
"ff83e13a-b256-4be2-ba5d-028d3f0ab450"
Subnet ID for load balancer. If not specified, any subnet from vip_network_id
will be selected. Ignored when vip_network_id
is not specified.
"4e7802d3-5023-44b8-b298-7726558fddf4"
Response
List of created tasks
List of task IDs
["d478ae29-dedc-4869-82f0-96104425f565"]