azure: default to TrustedLaunch VMs when DisableCVM is true - #3258
Merged
Conversation
Instead of defaulting to normal VMs, default to TrustedLaunch. When DisableCVM is false, the ConfidentialVM security profile with VMGuestStateOnly disk encryption is applied. For standard VM sizes, a TrustedLaunch security profile with Secure Boot and vTPM is used instead. This also simplifies the security profile logic: TrustedLaunch is always set as the baseline (with SecureBoot and vTPM), and only upgraded to ConfidentialVM when the size supports it and CVM is not disabled. Signed-off-by: Emanuele Giuseppe Esposito <eesposit@redhat.com>
mkulke
approved these changes
Aug 26, 2026
bpradipt
approved these changes
Aug 27, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
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.
Instead of defaulting to normal VMs, default to TrustedLaunch.
When DisableCVM is false, the ConfidentialVM security profile with VMGuestStateOnly disk encryption is applied. For standard VM sizes, a TrustedLaunch security profile with Secure Boot and vTPM is used instead.
This also simplifies the security profile logic: TrustedLaunch is always set as the baseline (with SecureBoot and vTPM), and only upgraded to ConfidentialVM when the size supports it and CVM is not disabled.