Update load balancer pool member
Updates the specified member’s mutable settings. address, protocol_port and
subnet_id cannot be changed after creation. If no changes are detected, no task
is created and an empty task list is returned.
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
Path Parameters
Project ID
1
Region ID
1
Pool ID
"00000000-0000-4000-8000-000000000000"
Member ID
"00000000-0000-4000-8000-000000000000"
Body
Administrative state of the member. Omit to leave unchanged; false disables the member so it receives no traffic.
true
false
Set to true if the member is a backup member, to which traffic will be sent exclusively when all non-backup members will be unreachable. Omit to leave unchanged.
true
false
Alternate IP address used for health monitoring of a backend member. Set to null to clear it and fall back to the member address; omit to leave unchanged.
Alternate protocol port used for health monitoring of a backend member. Set to null to clear it and fall back to the member protocol_port; omit to leave unchanged.
1 <= x <= 65535Member weight. Valid values are 0 < weight <= 256. Omit to leave unchanged. Controls traffic distribution based on the pool's load balancing algorithm:
ROUND_ROBIN: Distributes connections to each member in turn according to weights. Higher weight = more turns in the cycle. Example: weights 3 vs 1 = ~75% vs ~25% of requests.LEAST_CONNECTIONS: Sends new connections to the member with fewest active connections, performing round-robin within groups of the same normalized load. Higher weight = allowed to hold more simultaneous connections before being considered 'more loaded'. Example: weights 2 vs 1 means 20 vs 10 active connections is treated as balanced.SOURCE_IP: Routes clients consistently to the same member by hashing client source IP; hash result is modulo total weight of running members. Higher weight = more hash buckets, so more client IPs map to that member. Example: weights 2 vs 1 = roughly two-thirds of distinct client IPs map to the higher-weight member.
x <= 2561
Response
OK
List of task IDs representing asynchronous operations. Use these IDs to monitor operation progress:
GET /v1/tasks/{task_id}- Check individual task status and details Poll task status until completion (FINISHED/ERROR) before proceeding with dependent operations.