Resources / BackupVerification

BackupVerification

Whether the newest backup of a store was opened with the store's key and found restorable, and how long ago (spec 0036 'Backups', spec 0047 section 8). The status is kept from the manifest the backup Worker writes next to every export; Ready is false when the verification failed or is older than maxAgeSeconds.

Overview

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

Minimal example

apiVersion: platform.etorm.com/v1alpha1
kind: BackupVerification
metadata:
  name: example
spec:
  store: api

Spec

FieldTypeRequiredDefaultAllowedDescription
storestring (one of)yesapi, authWhich store's backups.
maxAgeSecondsinteger7200at least 60How old the last successful verification may be before the record is not Ready.

Status

FieldTypeRequiredDefaultAllowedDescription
observedGenerationintegerThe generation of the spec this status describes.
backupAtintegerUnix time the newest backup was made.
verifiedAtintegerUnix time of the key holder's verification of it.
okbooleanWhether the verification succeeded.
messagestringWhy it failed, or what is missing.
revisionintegerThe store's revision in the backup.
keysintegerNumber of keys in the backup.
bytesintegerSize of the sealed export.
conditionslist of objectReady and Degraded.
conditions[].typestringReady or Degraded.
conditions[].statusstringTrue, False or Unknown.

Columns in listings

ColumnFrom
Store.spec.store
Ready.status.conditions[?(@.type=='Ready')].status
Revision.status.revision
Verified.status.verifiedAt

All resources