List load balancers in a project.
curl --request GET \ --url 'https://stratum.example.com/v1/projects/example/lb/load-balancers?limit=100' \ --header 'Authorization: Bearer <token>'Cursor-paginated. Ordered name, id.
Ordering on name alone is not total, so id is the tiebreaker. Without a unique tiebreaker a cursor sitting on a tie repeats or
skips a row.
When nextPageToken is present there are more rows; pass it back as
page_token. A token that cannot be parsed is treated as no token, so a
client gets the first page rather than a 400.
This endpoint returned every matching row with no limit of any kind until .
Authorizations
Section titled “Authorizations”Parameters
Section titled “Parameters”Path Parameters
Section titled “Path Parameters”Query Parameters
Section titled “Query Parameters”Opaque cursor from a previous response’s nextPageToken. Omit for the
first page.
Responses
Section titled “Responses”Load balancers.
object
object
Set when a platform resource manages this row; absent on a tenant’s own.
object
The owner: the Auto Scaling group id, or for platform the component (front-door, pack:platform-health, default-network, operator-recipe).
Synthesized stable name for this LB. NOT resolvable until a Stratum DNS service publishes it — check dnsPublished before using it.
Whether dnsName is actually published to a resolver. Always false today (Stratum has no DNS service yet) — reach the LB via floatingIpId (internet-facing) or internalIp (internal). Flips per-LB once an LB-to-DNS publisher exists.
object
Why the load balancer is not active: the last placement failure, verbatim, or what it is waiting for once placed, such as its node’s report that the data-plane container runs and its floating IP is routed. Absent once active.
Example
{ "items": [ { "ownedBy": { "kind": "auto-scaling-group" }, "type": "application", "scheme": "internet-facing", "dataplaneIsolation": "shared" } ]}