-
Notifications
You must be signed in to change notification settings - Fork 5
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.
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
Add proposal for snapshot support #802
base: main
Are you sure you want to change the base?
Conversation
- Introduce `Snapshot` and `SnapshotClass` resources to allow users to take point-in-time snapshots of the content of a `Volume` - Enhance the `Volume` resource to include a `dataSource` field for restoring data from a snapshot - Improve data protection and disaster recovery capabilities - Provide support for different types of snapshots based on `VolumePool` capabilities - The proposal does not modify existing `VolumePool` resources - The `Snapshot` resource is not designed to provide a complete backup or archival solution for `Volumes` - The actual creation and readiness of a snapshot can depend on various factors such as `Volume` size, `VolumePool` capabilities, and infrastructure performance - The `Snapshot` resource and restoration path are meant to be additional tools in the data protection toolbox, not to replace existing comprehensive disaster recovery and data protection solutions Signed-off-by: Andreas Fritzler <[email protected]>
We have discussed the PR internally and do not see a problem with going forward as-is. We do not recommend going forward with the mentioned alternatives as its either off-loading significant portions to the user (3rd party provider), complicate interaction (storage provider APIs) or restrict flexibility (adding to |
volumeRef: | ||
name: example-volume | ||
snapshotClassRef: | ||
name: example-snapshotclass |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Can we also have encryption support for Snapshot as Volume encryption support is there?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I would expect a transitive behavior here. If the volume is encrypted, the snapshot should be encrypted as well. Plus, the option to encrypt the snapshot explicitly.
Proposed Changes
Snapshot
andSnapshotClass
resources to allow users to take point-in-time snapshots of the content of aVolume
Volume
resource to include adataSource
field for restoring data from a snapshotVolumePool
capabilitiesVolumePool
resourcesSnapshot
resource is not designed to provide a complete backup or archival solution forVolumes
Volume
size,VolumePool
capabilities, and infrastructure performanceSnapshot
resource and restoration path are meant to be additional tools in the data protection toolbox, not to replace existing comprehensive disaster recovery and data protection solutionsFixes #801