-
Notifications
You must be signed in to change notification settings - Fork 213
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
Support AMD SEV_SNP machines on GCP #1324
base: master
Are you sure you want to change the base?
Conversation
Hi @bgartzi. Thanks for your PR. I'm waiting for a openshift member to verify that this patch is reasonable to test. If it is, they should reply with Once the patch is verified, the new status will be reflected by the I understand the commands that are listed here. 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-sigs/prow repository. |
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: The full list of commands accepted by this bot can be found here.
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
Replacing openshift/api by a personal fork. In such, sev, sev-snp, and tdx specific confidentialCompute values have been added to the openshift api.
Extend gcpConfidentialComputeSupportedMachineSeries to also consider c3d machines capable of running SEV confidential machines.
Additional logic to support AMD SEV and AMD SEV-SNP values in the confidentialCompute parameter.
Still waiting for openshift/api#2165 to be merged. I will update the I'm keeping the TDX implementation apart in #1326. Should I bring it here and close that PR instead? cc @damdo and @JoelSpeed as you were the ones involved in the upstream patch review. |
Only AMD SEV nodes could be provisioned on GCP by machine api operator through the
confidentialCompute
Enabled/Disabled
flag.GCP also supports the
confidentialInstanceType
, which lets users choose the confidential computing technology. The latter precedesconfidentialCompute
. That is, ifconfidentialCompute=Disabled
is configured together with a validconfidentialInstanceType
, GCP will provision confidential VM.The validation webhook added in this patch mimics that behavior, so it's similar to the way GCP will handle it.
This patch complements openshift/machine-api-provider-gcp#107.
There's also a kubernetes-sigs/cluster-api-provider-gcp#1410 patch submitted.
Note the
openshift/api
ingo.mod
has been just replaced. The PR foropenshift/api
openshift/api#2165, hasn't been merged yet. I would update it properly when the PR is merged.Meanwhile, it also updates the list of machines that support SEV confidential computing, as
c3d
machines support it too.