-
Notifications
You must be signed in to change notification settings - Fork 159
Add CMEK support #211
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 CMEK support #211
Conversation
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: saad-ali The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
/hold |
4cfd8a6
to
79a94ce
Compare
Manually verified that encrypted disk is able to be provisioned via dynamic provision, used by a pod, and automatically deleted when pod and PVC are deleted /hold cancel |
/test pull-gcp-compute-persistent-disk-csi-driver-e2e |
1 similar comment
/test pull-gcp-compute-persistent-disk-csi-driver-e2e |
CapacityBytes: common.GbToBytes(20), | ||
VolumeId: testVolumeId, | ||
VolumeContext: nil, | ||
AccessibleTopology: stdTopology, |
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.
Is the Key something that would be ok/useful to add as part of the VolumeContext?
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.
It is not necessary. Once a volume is provisioned, GCE knows that the key is required and it does not explicitly need to be passed in for attach or mount.
/assign |
@davidz627 any idea why |
looks like its timing out, not sure why your change would make it take much longer but the timeout (10m) is pretty short anyway, I'll bump it |
/lgtm |
/test pull-gcp-compute-persistent-disk-csi-driver-e2e |
Modify the
CreateVolume
code to accept a new opaque parameter:disk-encryption-kms-key
.The value of this new parameter must be the fully qualified identifier for the key that will be used to encrypt new disks (e.g.
projects/[KMS_PROJECT_ID]/locations/[REGION]/keyRings/[KEY_RING]/cryptoKeys/[KEY]
).The key must exist prior to provisioning.
E2E tests will be added in a follow-up PR (need to figure out how to enable KMS and provision key as part of test).
/assign @msau42