-
Notifications
You must be signed in to change notification settings - Fork 34
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
Bug 1884632: Adding BYOK disk encryption through DES #158
Conversation
@enxebre @ingvagabund PTAL |
@ingvagabund When running |
I had to grant
Command line:
From the portal I was able to confirm the encryption:
|
Make generate scripts were broken. We'll need to re-run the make generate on this patch set after this merges: #159 Otherwise, this change LGTM |
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.
this looks reasonable to me
/lgtm
Worth documenting the additional role |
StorageAccountType string `json:"storageAccountType"` | ||
type ManagedDiskParameters struct { | ||
StorageAccountType string `json:"storageAccountType"` | ||
DiskEncryptionSet *DiskEncryptionSetParameters `json:"diskEncryptionSet,omitempty"` |
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 would be nice if we can provide details on what kind of permissions are required to use this disk encryption set for this machine.
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.
The service principal that is used with the cluster will require the reader role on the disk encryption set.
https://docs.microsoft.com/en-us/azure/aks/azure-disk-customer-managed-keys#grant-the-diskencryptionset-access-to-key-vault
} | ||
|
||
type DiskEncryptionSetParameters struct { | ||
ID string `json:"id,omitempty"` |
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.
Would be nice to include some documentation on the the expected form of the ID, Using Azure resource IDs implies that this resource can be from any subscription, any resource group.
Since this is for supporting customer managed encryption, it is fair to say we need to support this resource from resource group other than the cluster's but what about the subscription.
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.
Here is an example of an a disk encryption set ID. Azure resource IDs include a path-like system so that it is clear where the object is located, what the object is, and its name.
/subscriptions/<subscriptionid>/resourceGroups/disk-encryption/providers/Microsoft.Compute/diskEncryptionSets/aro-de
According to the documentation here https://docs.microsoft.com/en-us/azure/virtual-machines/linux/disk-encryption-key-vault#create-a-key-vault it states:
Your key vault and VMs must be in the same subscription. Also, to ensure that encryption secrets don't cross regional boundaries, Azure Disk Encryption requires the Key Vault and the VMs to be co-located in the same region. Create and use a Key Vault that is in the same subscription and region as the VMs to be encrypted.
Rebased with #158, |
I guess I need to add the |
407534a
to
9a07101
Compare
Looks like flakes under both e2e-azure and the operator:
|
/test e2e-azure-operator |
1 similar comment
/test e2e-azure-operator |
/test e2e-azure |
1 similar comment
/test e2e-azure |
@elmiko @michaelgugino Any ideas why this continues to fail? It looks like must-gather is failing. This PR only adds fields but isn't actually exercised. Is this inherently flaky? What do we do to get this to pass? If there is something wrong with the PR I'm happy to fix it. Can these tests be run locally? Just looking for some help. |
/test govet |
/retest Please review the full test history for this PR and help us cut down flakes. |
2 similar comments
/retest Please review the full test history for this PR and help us cut down flakes. |
/retest Please review the full test history for this PR and help us cut down flakes. |
@kwoodson: The following test failed, say
Full PR test history. Your PR dashboard. Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here. |
/retest Please review the full test history for this PR and help us cut down flakes. |
21 similar comments
/retest Please review the full test history for this PR and help us cut down flakes. |
/retest Please review the full test history for this PR and help us cut down flakes. |
/retest Please review the full test history for this PR and help us cut down flakes. |
/retest Please review the full test history for this PR and help us cut down flakes. |
/retest Please review the full test history for this PR and help us cut down flakes. |
/retest Please review the full test history for this PR and help us cut down flakes. |
/retest Please review the full test history for this PR and help us cut down flakes. |
/retest Please review the full test history for this PR and help us cut down flakes. |
/retest Please review the full test history for this PR and help us cut down flakes. |
/retest Please review the full test history for this PR and help us cut down flakes. |
/retest Please review the full test history for this PR and help us cut down flakes. |
/retest Please review the full test history for this PR and help us cut down flakes. |
/retest Please review the full test history for this PR and help us cut down flakes. |
/retest Please review the full test history for this PR and help us cut down flakes. |
/retest Please review the full test history for this PR and help us cut down flakes. |
/retest Please review the full test history for this PR and help us cut down flakes. |
/retest Please review the full test history for this PR and help us cut down flakes. |
/retest Please review the full test history for this PR and help us cut down flakes. |
/retest Please review the full test history for this PR and help us cut down flakes. |
/retest Please review the full test history for this PR and help us cut down flakes. |
/retest Please review the full test history for this PR and help us cut down flakes. |
@kwoodson: All pull requests linked via external trackers have merged: Bugzilla bug 1884632 has been moved to the MODIFIED state. In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
This pull requests adds fields to the v1beta1 types to suppert disk encryption sets.
We have customers requesting that we provide OS disk encryption. AKS is using DES for OS level as well as PVC support. The following PR was an attempt to add the necessary fields for bring-your-own-key encryption using DiskEncryptionSets.
This is high priority for the ARO team and we would like to get the work going.