Skip to content
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.

Sign up for GitHub

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

Jump to bottom

gcp: Support TDX confidential computing machine configuration #2193

Closed
wants to merge 2 commits into from
Closed

gcp: Support TDX confidential computing machine configuration #2193

wants to merge 2 commits into from

Conversation

bgartzi
Copy link
Contributor

@bgartzi bgartzi commented Feb 4, 2025 •
edited
Loading

Please, ignore. Do not merge. This is some work in progress.

This patch depends on #2165

Note that a commit from that PR is added in this PR.

I'm not sure if I should rather keep things separated, or close this PR and add the TDX-related commit into the other PR.

@openshift-ci openshift-ci bot added the size/M Denotes a PR that changes 30-99 lines, ignoring generated files. label Feb 4, 2025
@openshift-ci openshift-ci bot requested review from bparees and JoelSpeed February 4, 2025 08:12
@openshift-ci OpenShift CI
Copy link
Contributor

openshift-ci bot commented Feb 4, 2025

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: bgartzi
Once this PR has been reviewed and has the lgtm label, please assign sjenning for approval. For more information see the Code Review Process.

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 /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@openshift-ci OpenShift CI
Copy link
Contributor

openshift-ci bot commented Feb 4, 2025

Hello @bgartzi! Some important instructions when contributing to openshift/api:
API design plays an important part in the user experience of OpenShift and as such API PRs are subject to a high level of scrutiny to ensure they follow our best practices. If you haven't already done so, please review the OpenShift API Conventions and ensure that your proposed changes are compliant. Following these conventions will help expedite the api review process for your PR.

@openshift-ci openshift-ci bot added the needs-ok-to-test Indicates a PR that requires an org member to verify it is safe to test. label Feb 4, 2025
@openshift-ci OpenShift CI
Copy link
Contributor

openshift-ci bot commented Feb 4, 2025

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 /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

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.

@bgartzi
Copy link
Contributor Author

bgartzi commented Feb 4, 2025

/hold

@openshift-ci openshift-ci bot added the do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. label Feb 4, 2025
@bgartzi
Support SEV_SNP confidential type selection on GCP
b9662e4 
GCP compute API permits not only specifying whether a machine has to be
confidential or not, but also determining the technology backing that
up see [0]. This commit adds the possibility of not only Enabling or
Disabling confidential computing nodes, but also choosing the type of
confidential computing instances that are to be configured.

That way, configuring SEV_SNP machines should be possible as well as SEV
machines as previously.

[0] https://cloud.google.com/confidential-computing/confidential-vm/docs/supported-configurations
@bgartzi
Support TDX confidential type selection on GCP
aebea81 
GCP supports provisioning TDX confidential computing machines apart from
the previously supported AMD possibilities.

In this commit, another configuration option is added to the
confidentialCompute field so Intel TDX machines can be also configured.

Signed-off-by: Beñat Gartzia Arruabarrena <[email protected]>
@openshift-ci openshift-ci bot added size/S Denotes a PR that changes 10-29 lines, ignoring generated files. and removed size/M Denotes a PR that changes 30-99 lines, ignoring generated files. labels Feb 24, 2025
@bgartzi bgartzi mentioned this pull request Feb 24, 2025
Merged
@bgartzi bgartzi changed the title [DNM] Support TDX confidentialInstanceTypes gcp: Support TDX confidential computing machine configuration Feb 24, 2025
@bgartzi
Copy link
Contributor Author

bgartzi commented Feb 25, 2025

Closing this PR as the patch is being reviewed in #2165

@bgartzi bgartzi closed this Feb 25, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers

@bparees bparees Awaiting requested review from bparees

@JoelSpeed JoelSpeed Awaiting requested review from JoelSpeed

Assignees
No one assigned
Labels
do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. needs-ok-to-test Indicates a PR that requires an org member to verify it is safe to test. size/S Denotes a PR that changes 10-29 lines, ignoring generated files.
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
1 participant
@bgartzi