Resources / DeployedVersions

DeployedVersions

What the platform deployed and when, generated from the histories of its releases (spec 0047 section 3): the one record of what runs, so nobody writes it by hand. The release controller keeps the status; there is one object, `platform`.

Overview

APIplatform.etorm.com/v1alpha1
Resourcedeployedversions (cluster-scoped inside its cluster)
Short namesdepl
Available inthe platform only
Statuswritten by a controller through /status

Minimal example

apiVersion: platform.etorm.com/v1alpha1
kind: DeployedVersions
metadata:
  name: example
spec: {}

Spec

No fields.

Status

FieldTypeRequiredDefaultAllowedDescription
observedGenerationintegerThe generation of the spec this status describes.
rowslist of objectThe last 200 transitions of all releases, oldest first.
rows[].atintegerUnix time.
rows[].componentstringThe component.
rows[].fromstringThe version before.
rows[].tostringThe version after.
rows[].outcomestringuploaded, canary, promoted, rolled-back, drift, deployed, route-created and so on.
rows[].commitstringThe release's commit (first 12 digits).
rows[].releasestringThe release.
rows[].bystringWho or what decided.
markdownstringThe same rows as a markdown table, for the progress record.
conditionslist of objectReady.
conditions[].typestringReady.
conditions[].statusstringTrue, False or Unknown.

Columns in listings

ColumnFrom
Ready.status.conditions[?(@.type=='Ready')].status

All resources