-
Notifications
You must be signed in to change notification settings - Fork 467
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
aws kms - only works with storage in S3 #1541
Comments
andre-lx
changed the title
aws - only works with storage in S3
aws kms - only works with storage in S3
Feb 11, 2022
Thank you for your contribution! This issue has been automatically marked as |
github-actions
bot
added
the
lifecycle/stale
Denotes an issue or PR that has become stale and will be auto-closed.
label
Apr 7, 2024
akijakya
removed
the
lifecycle/stale
Denotes an issue or PR that has become stale and will be auto-closed.
label
Apr 25, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Describe the bug:
Hello. We are trying to set the storage as a folder/pv in the cluster, and use the s3 unseal config, but till now, we can only achieve this using also the storage as s3 as in the example:
https://github.com/banzaicloud/bank-vaults/blob/ea6352f8f71b4a364ffa6a3ea9fd67cb73ec490c/operator/deploy/cr-aws.yaml#L15-L33
Why can't we use s3 to store the keys and a folder for the remaining vault files?
Expected behaviour:
It should be possible to use s3 only to store the keys
Environment details:
/kind bug
The text was updated successfully, but these errors were encountered: