DRAFT: Support installation on SEV SNP confidential nodes #9395
Conversation
+ mod tidy + mod vendor
This will let choose sev or sev-snp as the confidential computing
technology of choice.
The way it behaves together with confidentialCompute is due to 2
reasons:
- Backwards compatibility.
- Mimicing the wave the GCP API behaves.
openshift-ci
bot
added
the
needs-ok-to-test
|
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 |
This patch series aims to support installing a cluster on AMD SEV SNP confidential nodes.
Previously, only AMD SEV nodes were supported, which were configured through the
confidentialComputeconfiguration flag.Now that GCP supports specifying the confidential instance type, we are letting users specify which node type (SEV/SEV-SNP) they would like to deploy the cluster on.
This series depend on the following patches:
kubernetes-sigs/cluster-api-provider-gcp#1410
openshift/api#2165
I will update the
go.modreplace sections pointing to personal forks once they are accepted.