TRITON-2529

Add support in CLB for configuring global timeouts via metadata

Status:
Resolved
Created:
2025-12-16T10:32:05.486-0500
Updated:
2026-01-05T13:09:06.681-0500

Description

Coming from the EC side of the house, so I’ll be scribbling ticket data in here on behalf of Ben Lovett ( blovett-ec ).

Cloud-load-balancer (aka. triton-moirai) needs the ability to change haproxy timeouts via metadata (and therefore via CLOUDAPI and triton-cli). Additionally, some documentation needs updating due to an error (“triton instance update” is the error, “triton instance set” is correct).

Comments (2)

Dan McDonald commented on 2025-12-16T13:47:36.247-0500:

The fix for this ticket adds a cloud.tritoncompute:timeouts key to the metadata for a CLB instance. That key expects a JSON object with four possible fields. From the documentation updates:

Parameter

Default

Description

queue

0

Time (ms) to wait in queue for a connection slot. 0 = unlimited

connect

2000

Time (ms) to wait for a connection to be established to a backend

client

55000

Client inactivity timeout (ms)

server

120000

Server response timeout (ms)

Dan McDonald commented on 2025-12-17T13:08:08.176-0500:

The actual assignee is Ben Lovett, who doesn’t have MNX Jira access.