The module lifecycle stageGeneral Availability

The module has requirements for installation

v1.0.0

  • First release, at the General Availability level. The module captures the entire state of a namespace, both its object manifests and its volume data. A snapshot is a tree in which each node is served by the module that owns it.
  • An object that must not go into a snapshot carries the state-snapshotter.deckhouse.io/exclude label. The value of the label is ignored; the key alone is enough.
  • A snapshot can be downloaded and uploaded back, and the module hands out its manifests ready to apply, with references already rewritten. The module does not resolve conflicts with what the target namespace already holds; a client does that, either d8 or the web console.
  • Enabled automatically in the Default, Managed and Minimal bundles, so basic backup functionality is always available.
  • Requires Deckhouse >= 1.76.9, the release that ships a compatible d8 CLI. On anything earlier the module does not activate.
  • Snapshots are not for the cluster administrator alone. Anyone granted the matching permissions can work with them.

v0.1.7

  • Updating container-base images to v1.1.2

v0.1.6

  • Update base images, Go 1.25.10 and lib-helm 1.71.12
  • Internal changes in module assembly

v0.1.5

  • Internal changes in module structure and assembly

v0.1.4

  • Update base images, Go 1.25.10 and lib-helm 1.71.11
  • Internal changes to the module assembly

v0.1.3

  • Corrections to the module structure

v0.1.2

  • Controller: TTL processing moved to MCR; IRetainer replaced with ObjectKeeper
  • Mount points in distroless images; updating base images, Go and lib-helm
  • CI changes: DistroPackagesProxy and env proxy in werf, improvements to CVE scans and auxiliary workflows
  • Added user-authz cluster roles in templates

v0.1.1

  • Small fix in module structure

v0.1.0

  • Initial release