Change snapshot retention
Set how many snapshot generations Telark keeps per application, and keep noisy namespaces out of the snapshot volume.
Telark keeps the last 5 snapshot generations per application by default. Raise the number to roll back further; lower it to save space on the snapshot volume.
You need: the Contributor role or higher on Settings.
1. Check current usage
Open Settings → Governance → Snapshot storage. The bar shows the volume's capacity, used and available space, and the snapshot count.
An application's Manage Snapshots panel shows the size of each snapshot. Multiply the average size by the new limit and by your number of applications to estimate the space you need.
2. Change the limit
- In Snapshot storage, set the number of snapshots to keep per application.
- Choose Save snapshots.
The value is stored as spec.snapshots.maxPerApp on the TelarkConfig named default.
3. Know when it applies
Nothing is deleted when you save. Each application is pruned the next time it records a change: Telark adds the new generation, drops the oldest generations above the limit, and deletes their files from the volume. An application that never changes keeps its snapshots.
The limit counts generations, and a generation is kept or dropped as a whole. An application that spans two namespaces keeps up to 5 snapshots in each namespace, so a rollback never restores only one of them.
Keep noisy namespaces out
Workloads in an excluded namespace are never discovered, so they never produce snapshots. Add namespaces under Settings → Governance → Excluded namespaces (spec.excludedNamespaces). default, kube-system, kube-public and kube-node-lease are excluded out of the box.
Choosing a value
| Limit | Good for |
|---|---|
| 5 (default) | Rolling back recent changes |
| 10 to 20 | Slow-moving applications where the good state may be days back |
| More | Rarely worth it. Use a backup tool such as Velero for long-term recovery |
Retention is one cluster-wide number, counted in generations, not days. The snapshot volume is a rollback store, not a compliance archive: if you need a long-term audit trail, keep your own copy.
If the volume fills up
Lower the limit, then expand the PVC if your storage class supports it. See Troubleshooting.