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

Update backupstoragelocation.md SSE-C #176

Merged
merged 1 commit into from
Nov 13, 2023
Merged

Update backupstoragelocation.md SSE-C #176

merged 1 commit into from
Nov 13, 2023

Conversation

MrOffline77
Copy link
Contributor

  • During setup of SSE-C I discovered strange behavior and unclear documentation on how to configure SSE-C
  • I read the code where SSE-C came in Add SSE-C encryption support #96 and updated the description so other people get a chance to understand how this works. The Author of Add SSE-C encryption support #96 implemented this for Helm Charts as far as I understood, but when using velero install instead of helm, things get confusing on how to setup SSE-C properly.
  • I assumed that the referenced file customerKeyEncryptionFile transforms into a secret when used with velero install like the secret-file file which holds the S3 creds. But instead its referencing the path to the secret from the within the velero pod.

Signed-off-by: Malte <malte.graebner@outlook.com>
@reasonerjt reasonerjt closed this Nov 13, 2023
@reasonerjt reasonerjt reopened this Nov 13, 2023
@reasonerjt reasonerjt merged commit 67653e5 into vmware-tanzu:main Nov 13, 2023
4 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
3 participants