Skip to content

Add reclaim policy requirement for snapshots #3509

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 2 commits into from
Sep 3, 2025
Merged

Add reclaim policy requirement for snapshots #3509

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
5a81be3
Add reclaim policy requirement for snapshots
sgalsaleh Sep 3, 2025
99c4939
docs edits
paigecalvert Sep 3, 2025
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
11 changes: 11 additions & 0 deletions docs/vendor/snapshots-configuring-backups.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -4,6 +4,17 @@ This topic provides information about how to configure the Velero Backup resourc

For more information about snapshots, see [About Backup and Restore with snapshots](/vendor/snapshots-overview).

## Storage Class Requirement

For backup and restore operations to work properly, PersistentVolumes must use a StorageClass with a reclaim policy of `Delete`. Backup and restore operations are not supported for volumes with `Retain` reclaim policy.

To verify your StorageClass reclaim policy, run:
```bash
kubectl get storageclass -o wide
```

If needed, update the StorageClass reclaim policy to `Delete` before configuring snapshots.

## Configure Snapshots

Add a Velero Backup custom resource (`kind: Backup`, `apiVersion: velero.io/v1`) to your release and configure it as needed. After configuring the Backup resource, add annotations for each volume that you want to be included in backups.
Expand Down