Global network address map (IPAM view).
curl --request GET \ --url https://stratum.example.com/v1/admin/network/address-map \ --header 'Authorization: Bearer <token>'An aggregated, operator-facing view of every CIDR and notable
host address Stratum knows about: reserved infrastructure ranges (mgmt
plane, cluster plane, CGNAT transit), the per-VPC transit supernet, VPC
primary and secondary CIDRs, subnets, floating-IP pools (runtime, meta,
per-project), and allocated floating IPs. Each entry is labeled with a
kind, a human purpose, its owner (a projectId or infra), and
cross-references. Use contains to answer “what claims this address?”.
Install-scope; gates on network:GetAddressMap.
Authorizations
Section titled “Authorizations”Parameters
Section titled “Parameters”Query Parameters
Section titled “Query Parameters”An IP or CIDR; returns only entries whose CIDR overlaps it.
Narrow VPC/subnet/floating-IP entries to one region.
Responses
Section titled “Responses”The aggregated address map.
object
One CIDR (or single host address as /32) in the global address map.
object
The CIDR; single host addresses are rendered as /32.
What the entry is.
Human-readable description.
A projectId, or infra for Stratum-owned ranges.
Lifecycle state where applicable.
Cross-references (vpcId, subnetId, poolId, fipId,…).
object
utilization roll-up, present only on entries with a countable address space (subnets + floating-IP pools). Absent on infra ranges and single-IP entries. Feeds the IPAM utilization bars.
object
Addresses in the CIDR / pool size.
Addresses in use.
Addresses still assignable.
True when one of the underlying LIST queries hit the row ceiling, so the map may be incomplete (cursor pagination is a 2.0 follow-on).
Example
{ "entries": [ { "kind": "reserved-infra", "scope": "global" } ]}Authenticated but not authorized.
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" } ]}