Documentation for ephemeral-storage (#8244)
Some checks failed
Run the E2E test on kind / build (push) Failing after 6m0s
Run the E2E test on kind / setup-test-matrix (push) Successful in 3s
Run the E2E test on kind / run-e2e-test (push) Has been skipped
Main CI / Build (push) Failing after 31s
Close stale issues and PRs / stale (push) Successful in 10s
Trivy Nightly Scan / Trivy nightly scan (velero, main) (push) Failing after 1m9s
Trivy Nightly Scan / Trivy nightly scan (velero-plugin-for-aws, main) (push) Failing after 42s
Trivy Nightly Scan / Trivy nightly scan (velero-plugin-for-gcp, main) (push) Failing after 57s
Trivy Nightly Scan / Trivy nightly scan (velero-plugin-for-microsoft-azure, main) (push) Failing after 52s

Signed-off-by: MICHAEL S FRUCHTMAN <msfrucht@us.ibm.com>
This commit is contained in:
Michael Steven Fruchtman
2025-06-06 07:25:42 -07:00
committed by GitHub
parent b58dbcb0b8
commit 9a9574325b
2 changed files with 12 additions and 0 deletions

View File

@@ -178,6 +178,12 @@ Additionally, you may want to update the the default File System Backup operatio
- --fs-backup-timeout=240m
```
### Ephemeral-storage Requests and Limits
Velero does not set ephemeral-storage limits during installation. Limits and requests can be edited after install for clusters that monitor and restrict ephemeral-storage usage.
Plugins will use ephemeral-storage. There needs to be a sufficient requests and limit set to account for plugins and the additional ephemeral-storage used to maintain credentials and cache space for datamovers. Object storage plugins will fit comfortably into an allocation of 100MB of ephemeral-storage.
## Configure more than one storage location for backups or volume snapshots
Velero supports any number of backup storage locations and volume snapshot locations. For more details, see [about locations](locations.md).

View File

@@ -178,6 +178,12 @@ Additionally, you may want to update the the default File System Backup operatio
- --fs-backup-timeout=240m
```
### Ephemeral-storage Requests and Limits
Velero does not set ephemeral-storage limits during installation. Limits and requests can be edited after install for clusters that monitor and restrict ephemeral-storage usage.
Plugins will use ephemeral-storage. There needs to be a sufficient requests and limit set to account for plugins and the additional ephemeral-storage used to maintain credentials and cache space for datamovers. Object storage plugins will fit comfortably into an allocation of 100MB of ephemeral-storage.
## Configure more than one storage location for backups or volume snapshots
Velero supports any number of backup storage locations and volume snapshot locations. For more details, see [about locations](locations.md).