Add support for running tests on confidential VMs that use NVMe #1636
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What type of PR is this?
/kind cleanup
What this PR does / why we need it:
This adds support to run e2e tests in a configuration that uses NVMe devices. Currently the e2e tests default to using
n2
machine family, which uses SCSI by default. Passing in the--enable-confidential-compute
flag is a cost effective way to use NVMe (an alternative being running againstc3-standard-4
machine type, but this requires additional test refactoring, or skipping tests, as there are restrictions on disk types).To support toggling with just the binary flag, this also updates the defaults of the test to use
n2d
as well as a Ubuntu guest OS image instead of Debian.Support for running "[NVMe]" tagged tests are presubmit will be added in kubernetes/test-infra#32214. These can also be run locally with:
Does this PR introduce a user-facing change?: