-
Notifications
You must be signed in to change notification settings - Fork 1.4k
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 immutability supporting limitation in documents. #6474
Conversation
Codecov Report
@@ Coverage Diff @@
## main #6474 +/- ##
==========================================
- Coverage 60.18% 59.81% -0.38%
==========================================
Files 229 236 +7
Lines 24219 25088 +869
==========================================
+ Hits 14577 15007 +430
- Misses 8634 9041 +407
- Partials 1008 1040 +32 |
3e9875e
to
8a670d3
Compare
This address the need to document the data immutability limitation in issue #6422. |
@draghuram |
Sorry for the delay, will take a look. |
I made some changes to the text. Please feel free to make more changes as you see fit. It is a very difficult topic to document but it is better to have something and then we can improve it. My versionStarting from 1.11, Velero's backups may not work as expected when the target object storage has some kind of an "immutability" option configured. These options are known by different names (see links below for some examples). The main reason is that Velero first saves the state of a backup as Note that backups may still work in some cases depending on specific provider and configuration.
The following are the links to cloud providers' documentation in this regard: |
@draghuram |
Signed-off-by: Xun Jiang <[email protected]>
Looks good. |
Thank you for contributing to Velero!
Please add a summary of your change
Does your change fix a particular issue?
Fixes #(issue)
Please indicate you've done the following:
/kind changelog-not-required
as a comment on this pull request.site/content/docs/main
.