-
Notifications
You must be signed in to change notification settings - Fork 70
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: Support LUKS encryption using IBM CEX secure keys on s390x #536
Conversation
Hi @travier , |
Hi @travier , |
|
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's coming along! a few nits;
Thank you for doing this.
Hi @prestist , |
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.
Gennerally lgtm I have like one nit; otherwise I think its gtg.
Docs rephrase in luks.cex.enabled description. coreos/butane#536 (comment)
Docs rephrase in luks.cex.enabled description. coreos/butane#536 (comment)
3ec0f5c
to
f6f2964
Compare
|
Hi, Is this pr ok to approve? or anything pending from my side? |
@madhu-pillai , I am going to run through and review from my perspective, but will not be merging until I hear from @travier since he had a lot of feedback, and I want to ensure his concerns are resolved. Note: the now latest version of ignition is 2.20.0 which has the functionality this sugar uses in stable, I would prefer to get this in before we update butane with that version and its new specs. |
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.
Hi @prestist , |
Hi @travier , Could you review the PR please? |
f6f2964
to
b833c52
Compare
OK, we need to split this in at least two commits:
|
OK, we can not update to 2.20 until we do #558 |
Hold on, I'm doing the rebase / resplit. |
This should be good now. I'll do another pass tomorrow. Then we need to stabilize all of that. |
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.
With the latest changes, lgtm.
@travier Makes sense, so to be clear, we land this pr then separately stabilize? (preferred) I don't want to stabilize in this pr. |
Yes, if I'm not mistaken, we should follow this order (#550 (comment)): |
- Use "layout" in the context path for errors related to the layout entry in the boot_device configuration. - Add tests for those error cases. - Refactor mirror boot_device check for s390x. Fixes: coreos#484
Alright, I've added more tests and fixed the case where they failed so this should be ready now. |
For fcos 1.6.0-exp & openshift 4.18.0-exp specs, expected to be based on stable 3.5.0 spec. See: coreos/ignition#1693 See: coreos/fedora-coreos-tracker#1708
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.
Thank you for catching that/fixing it, and then adding tests. LGTM
fcos/1.6.0-exp: Fix context for boot_device.layout errors
entry in the boot_device configuration.
Fixes: #484
vendor: Update ignition/v2 v2.19.0 & aws-sdk-go v1.53.5
Support LUKS encryption using IBM CEX secure keys on s390x
For fcos 1.6.0-exp & openshift 4.18.0-exp specs, expected to be based on
stable 3.5.0 spec.
See: coreos/ignition#1693
See: coreos/fedora-coreos-tracker#1708