-
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 1900454: Add SecurityProfile.EncryptionAtHost parameter to enable host-based VM encryption #183
BUG 1900454: Add SecurityProfile.EncryptionAtHost parameter to enable host-based VM encryption #183
Conversation
@dkorzuno This PR seems to implement a feature similar to #158 which merged earlier during this release cycle. Disk encryption and this feature seem to be at odds with each other, ie, you can't use them at the same time. Are you aware of how the two features differ? It would be good to understand the motivation for supporting both |
@JoelSpeed yes, they're awfully similar, but not the same... #158 is about device encryption of attached VM disks using user managed keys, which is largely an enterprise requirement. The options are not mutually exclusive and I believe we have customer use cases for neither, either, and both. Aaaah! Thanks, Jim |
This is from the docs that are linked in the PR description, suggests to me that they are mutually exclusive and that you can't use both in tandem 🤔 Do we have an RFE for this feature? As far as I'm aware no one has brought this feature to the team's attention before raising this PR so we are a little unsure of what the drive is for adding this feature |
Azure Disk Encryption is yet another technology, it's different again to disk encryption sets (#158) and encryption at host (this PR). I understand that OpenShift doesn't and won't support ADE. Sorry there's no RFE :-/ Let's catch up about that tomorrow. |
Created a Bugzilla entry https://bugzilla.redhat.com/show_bug.cgi?id=1900454 |
/retitle BUG 1900454: Add SecurityProfile.EncryptionAtHost parameter to enable host-based VM encryption |
@dkorzuno: This pull request references Bugzilla bug 1900454, which is invalid:
Comment 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. |
/bugzilla refresh |
@JoelSpeed: This pull request references Bugzilla bug 1900454, which is valid. The bug has been moved to the POST state. 3 validation(s) were run on this bug
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. |
e6deb30
to
363b0d5
Compare
@JoelSpeed (or someone) could you help me identify what caused the e2e test fail? The build log says
but it's hard to trace it back to the change I made. |
I don't think this issue is related to your PR, let's give a restest and see if it fails in the same way again /retest |
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 latest changes look good btw, I like the extraction of the virtualMachineParameter creation into its own function, very clean. Test cases looking good too
return osProfile, nil | ||
} | ||
|
||
func DeriveVirtualMachineParameters(vmSpec *Spec, location string, subscription string, nic network.Interface) (*compute.VirtualMachine, error) { |
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 good to have a comment on top of this, also, probably doesn't need to be an exported method, deriveVirtualMachineParameters
should be sufficient
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.
Good point. Changes made.
updateSpec := tc.updateSpec | ||
validate := tc.validate |
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.
No need to declare these here is there? Can just use them inline?
363b0d5
to
84e94d6
Compare
@JoelSpeed I made the changes you requested. The e2e test is still failing though :( |
} | ||
|
||
for _, tc := range testCases { | ||
tc := tc |
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.
I don't think we have a loop capturing issue here, this isn't normally needed since the range variable is a reference not a pointer. You can test this by breaking one of the test cases and removing this line, only the one should fail, not all of them
The E2E failures are unrelated, it is a known issue that the tests are rather flaky at the moment, don't worry about them. FYI, I'm still waiting on PM direction as to whether we should be accepting this PR or not (CC @listey) |
…rameter to enable host-based VM encryption
84e94d6
to
6c9b028
Compare
/approve /hold until I get a response from PM about what to do here |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: JoelSpeed 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 |
Having spoken with PM, we should be able to merge this as soon as master opens for 4.8. Probably some time in February based on current schedules. Will try and get someone else from my team to give a review as well so it's ready to go when master opens |
This /lgtm Let's wait until the branch opens again. |
/hold cancel 4.8 master is now open so this can be merged |
/lgtm |
@dkorzuno: All pull requests linked via external trackers have merged: Bugzilla bug 1900454 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. |
/cherry-pick release-4.7 |
@mjudeikis: new pull request created: #201 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. |
/cherry-pick release-4.6 |
@mjudeikis: new pull request created: #202 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. |
What this PR does / why we need it:
The PR adds a parameter which enables encryption at host for virtual machines.
The corresponding upstream PR is kubernetes-sigs#1012
Special notes for your reviewer:
I am not sure how to go about unit testing the changes.
Release note: