Check the release mirror now.
curl --request POST \ --url https://stratum.example.com/v1/admin/upgrades/check \ --header 'Authorization: Bearer <token>'Records the request and returns at once (202) with what is known now; the
update check reads the mirror on its next pass, and
GET /v1/admin/upgrades/available shows the result (check.checkedAt,
or check.error). Refused (409 MirrorDisabled) while the check is off.
Install-scope; gates on upgrade:CheckForUpdates.
Authorizations
Section titled “Authorizations”Responses
Section titled “Responses”Recorded.
The releases on the mirror newer than the one the cluster runs, newest first, from the last index read. Empty while the check is off, and until the mirror set now has been read once.
object
The version the cluster runs (its oldest node); empty when not known.
The cluster runs a development build; every release is offered and none is compared with it.
Where the control plane looks for newer releases. It reads the mirror’s
signed release index every checkIntervalSeconds and lists the releases
newer than the cluster’s; it never installs one by itself.
object
The release mirror. The index is <url>/releases/stratum/index.json.
False turns the update check off, for an install without internet access.
How often the index is read.
The mirror used when none is set.
The update check. error is why the last attempt failed (empty when it
worked), errorKind unreachable (the mirror did not answer) or invalid
(its index did not verify, or is older than one already read from it). The
releases of the last index that verified stay listed.
object
The last “check now”.
When an index last verified.
Null while the check is off.
Where the listed releases come from: the mirror set, or with a release
token the stable channel (ReleaseToken.stableUrl), or the default
mirror when that channel refused the token.
The release key that signed the index.
A release on the mirror newer than the one the cluster runs.
object
feature is X.Y.0, a batch of features. fix and security are X.Y.Z
with fixes only; security fixes the vulnerabilities in cves.
When this cluster first saw the release on the mirror.
The release notes URL.
The oldest version that upgrades to this release directly.
No upgrade may skip this release; a cluster older than it upgrades to it first.
False when the cluster cannot upgrade to it directly; reason says why.
The way from the version the cluster runs to a release, from the
upgrade paths in the signed release index: direct, via the releases in
via first (a required stop, a minimum version), broken (a known-broken
upgrade: use use instead), reinstall (use starts the upgrade chain:
install it fresh from its ISO), unreachable, or unchecked (a development
build, a version not known, or no index that lists the release). The plan’s
upgrade-path precheck says the same.
object
The releases to upgrade to first, in order.
The ticket of a broken upgrade.
The release to upgrade to instead of a broken one; for reinstall, the
release that starts the upgrade chain, to install fresh.
Example
{ "running": "0.2.0", "mirror": { "url": "https://mirror.example.com", "checkIntervalSeconds": 21600, "defaultUrl": "https://mirror.example.com" }, "check": { "errorKind": "" }, "items": [ { "version": "0.3.0", "type": "feature", "cves": [ "CVE-2026-12345" ], "path": { "kind": "direct", "via": [ "0.3.0" ], "use": "0.2.3", "message": "0.2.1 cannot upgrade straight to 0.2.2: upgrade to 0.2.3 instead" } } ]}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" } ]}Conflicting state.
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" } ]}