The cluster's per-VPC DNS recursor replica setting, and how far it has converged.
curl --request GET \ --url https://stratum.example.com/v1/admin/network/dns/recursor-settings \ --header 'Authorization: Bearer <token>'How many replicas of each VPC’s recursor the cluster runs (1, or
2 for active/active), and the network-dns-recursor converger’s view of it:
whether every DNS VPC is at the setting, and how many replicas the .3
resolvers still balance to. Seeded once from STRATUM_DNS_RECURSOR_REPLICAS;
after that this setting is the only source. Install-scope; gates on
network:GetDNSRecursorSettings.
Authorizations
Section titled “Authorizations”Responses
Section titled “Responses”The setting and its status.
The cluster’s per-VPC recursor replica setting and the network-dns-recursor converger’s view of it.
object
The desired per-VPC replica count (always 1 on single-node).
The highest count this install accepts: 2 (the per-VPC DNS switch is a /29: a gateway and two replicas), 1 on single-node.
Moves on every change of replicas.
Seed: from STRATUM_DNS_RECURSOR_REPLICAS at first start; operator: set through this API.
How far the cluster has converged on the replica setting. Absent until the network-dns-recursor converger’s first pass.
object
Converged when the last pass found every DNS VPC at the setting, for the current generation: its switch has the setting’s ports and its .3 balances to as many replicas as placement holds (fewer on a cluster with fewer ready nodes). converging otherwise, including right after a change and while a replica does not answer.
The setting generation the last pass worked to.
The most replicas any VPC’s .3 still balances to. The recursor sweeps keep that many placed, so a replica is never removed while it still takes flows.
DNS-resolving VPCs the last pass covered.
The first VPC not at the setting, and why.
When the converger last recorded a change, or refreshed an unchanged status (at least every two minutes while it runs).
Example
{ "source": "seed", "status": { "phase": "converged" }}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" } ]}Upstream temporarily unavailable (driver / scheduler / dependency).
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" } ]}