Describe a load balancer.
curl --request GET \ --url https://stratum.example.com/v1/projects/example/lb/load-balancers/example \ --header 'Authorization: Bearer <token>'Authorizations
Section titled “Authorizations”Parameters
Section titled “Parameters”Path Parameters
Section titled “Path Parameters”Responses
Section titled “Responses”The load balancer.
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
{ "ownedBy": { "kind": "auto-scaling-group" }, "type": "application", "scheme": "internet-facing", "dataplaneIsolation": "shared"}Resource not found.
object
The findings of a rejected IAM policy document (custom and resource policies).
One finding of a rejected IAM policy document. A rejection lists every finding, so the author fixes the document in one round trip.
object
The finding, e.g. INVALID_DOCUMENT, UNKNOWN_ACTION, ACTION_NOT_APPLICABLE.
Index of the statement at fault; -1 for the document as a whole.
The offending action, where one is at fault (ACTION_NOT_APPLICABLE).
Field errors, for codes that carry them: each problem at its field
(see FieldError). Documented on the responses that set it, e.g.
approveNodeJoin’s INVALID_INPUT and JOIN_APPROVAL_REFUSED.
Absent otherwise.
One field’s problem, the stage-2 installer API’s shape.
field is the field’s path, message what is wrong with it.
object
The field’s path, e.g. links[0].interface, disks[1].confirm,
mgmt.address or role; empty for the whole request.
Structured facts about the refusal, for codes that carry them. The
shape is fixed per code and documented on the response that answers
it, e.g. IMAGE_POOL_MISMATCH (see ImagePoolMismatchDetails) and
IMAGE_IN_USE. Absent for codes that carry none.
object
Example
{ "issues": [ { "code": "ACTION_NOT_APPLICABLE", "action": "compute:CreateVpc" } ]}