-
Notifications
You must be signed in to change notification settings - Fork 6
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
Storage encryption proposal #603
Conversation
added storage encryption proposal
updated storage encryption proposal
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.
For me is the overall flow a bit unclear. Can you elaborate the interplay of a VolumePool
and a Volume
. Do you implicit assume that a VolumePool
is encrypted (that assigned volumes) if the secret in spec.encryption
is given? What is expected if the Volume
encryption flag is set to false and it is assigned to an "encrypted" pool?
As per discussion now encryption key secret reference will be provided in Volume.
|
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.
Up for discussion: behaviour when a user does not set a secret for a encrypted volume explicitely. I would prefer auto-generating an individual secret instead of relying on a shared secret in that case.
encryption key should be base64 encoded 256 bit key
Flow adjusted / concerns addressed.
Proposed Changes
Storage encryption proposal to enable onmetal volume encryption with user provided encryption key