docs(backups): say who applies a bucket lifecycle rule

The notes that send a tenant to a bucket lifecycle rule for a backup
object Cozystack leaves behind read as if some policy were already in
place. None is: the rule has to be set on the bucket, and it is applied
only by an object store that implements lifecycle, which the bundled
SeaweedFS now does once a day while lifecycle.enabled is on.

Assisted-by: LLM
Signed-off-by: Alexey Artamonov <aleksei.artamonov@aenix.io>
This commit is contained in:
Alexey Artamonov committed 2026-11-04 19:30:47 +03:00
1 parent f36d864e99
commit 27e0aa2880
3 files changed
+6 -11

No files matched your search

@@ -71,9 +71,6 @@ The script:
had already replayed. The Pod log names each topic before its replay and
again once it landed; empty or delete every topic it shows as started, not
only the one the refusal names, then re-run.
- The tarball in object storage is not managed by the Cozystack `Backup`
lifecycle: deleting the `Backup` CR removes the reference but leaves the S3
object in place. Tenants who need to reclaim space should delete the object
(or set a bucket lifecycle policy).
- The tarball in object storage is not managed by the Cozystack `Backup` lifecycle: deleting the `Backup` CR removes the reference but leaves the S3 object in place. Tenants who need to reclaim space should delete the object, or set a lifecycle rule on the bucket. The Cozystack SeaweedFS applies such rules once a day while its `lifecycle.enabled` is on, which is the default; another object store applies them only if it implements bucket lifecycle.
- Consumer-group offsets, topic configs, ACLs and users are not part of the
backup; consumers start from the restored topic's fresh offsets.
@@ -55,9 +55,6 @@ The script:
- Both flows rely on the strategy template branching on `.Mode`. See
`01-create-strategy.sh`.
- The tarball in object storage is not managed by the Cozystack `Backup`
lifecycle: deleting the `Backup` CR removes the reference but leaves the S3
object in place. Tenants who need to reclaim space should delete the object
(or set a bucket lifecycle policy).
- The tarball in object storage is not managed by the Cozystack `Backup` lifecycle: deleting the `Backup` CR removes the reference but leaves the S3 object in place. Tenants who need to reclaim space should delete the object, or set a lifecycle rule on the bucket. The Cozystack SeaweedFS applies such rules once a day while its `lifecycle.enabled` is on, which is the default; another object store applies them only if it implements bucket lifecycle.
- `nats stream restore` recreates the stream's configuration from the snapshot;
consumers are restored as captured at backup time.
@@ -1376,9 +1376,10 @@ func (r *BackupJobReconciler) createMongoDBBackupArtifact(
// annotation (honoured before any apiserver read, so it still frees a Backup
// whose operator CR has become unreadable) and a going-away namespace (the psmdb
// delete-backup exec cannot run there) each make the driver strip its own
// finalizer and release, leaving the object for a bucket lifecycle policy. This
// bounds only what the driver contributes: a Get that fails with something other
// than NotFound/NoMatchError still requeues (below), and the psmdb operator's own
// finalizer and release, leaving the object to a lifecycle rule on the bucket,
// if one is set, or to manual cleanup. This bounds only what the driver
// contributes: a Get that fails with something other than
// NotFound/NoMatchError still requeues (below), and the psmdb operator's own
// release-lock finalizer keeps the CR Terminating while the operator is down,
// whatever the driver strips. A down operator in a live namespace is likewise
// not auto-released: the Backup stays Terminating as a visible signal until an