Skip to content
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

To add a support of skipping/ignoring of any snapshot in an object lock enabled S3 bucket. #843

Open
ishan16696 opened this issue Feb 17, 2025 · 1 comment
Assignees
Labels
area/security Security related kind/enhancement Enhancement, improvement, extension

Comments

@ishan16696
Copy link
Member

How to categorize this issue?

/area security
/kind enhancement

What would you like to be added:
In this PR: #818, we have added support for handling AWS S3's object lock mechanism in the backup-restore, ensuring that snapshots are immutable. However, if users want backup-restore to skip or ignore certain snapshots, we need to implement a similar approach to what is currently available for other providers like GCS and ABS. These providers allow users to tag snapshots (with certain key), which they wish to be ignored by backup-restore . For more information, please refer to the documentation

Why is this needed:
When snapshots were mutable(if object lock isn't enabled), operators could simply delete any snapshots present in the object store, and subsequent restorations would not include them. However, once immutability is enabled, it is no longer possible to delete these snapshots. Hence, there should be a mechanism available for backup-restore to ignore any of snapshots during restoration.

@gardener-robot gardener-robot added area/security Security related kind/enhancement Enhancement, improvement, extension labels Feb 17, 2025
@ishan16696
Copy link
Member Author

/assign

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/security Security related kind/enhancement Enhancement, improvement, extension
Projects
None yet
Development

No branches or pull requests

2 participants