Repository navigation
DOC-3299: document the VM state StorageClass for persistent EFI and TPM - #12186
Merged
Merged
Conversation
VMs with persistent EFI variables or a persistent TPM need vmStateStorageClass or a default StorageClass. In VMO pack 4.10.x, VMO Manager owns the KubeVirt resource, so set the value in the 4.9.x values before upgrading or edit it on the KubeVirt Configuration page afterward. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
✅ Deploy Preview for docs-spectrocloud ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
Linus-SpectroCloud
marked this pull request as ready for review
October 12, 2026 12:19
Linus-SpectroCloud
requested review from
addetz,
benradstone and
spectro-gh-kdawn
October 12, 2026 12:19
Contributor
|
✅ Slack reviewers notified at 2026-10-12T12:20:56Z \n |
Contributor
|
✅ CI checks passed for commit 4b8cc8d. |
benradstone
approved these changes
Oct 12, 2026
Linus-SpectroCloud
enabled auto-merge (squash)
October 12, 2026 13:18
Contributor
|
✅ CI checks passed for commit 07f8647. |
Contributor
|
✅ CI checks passed for commit 8e185ac. |
Contributor
💚 All backports created successfully
Note: Successful backport PRs will be merged automatically after passing CI. Questions ?Please refer to the Backport tool documentation and see the Github Action logs for details |
vault-token-factory-spectrocloud Bot
added a commit
that referenced
this pull request
Oct 12, 2026
…PM (#12186) (#12209) * DOC-3299: document the VM state StorageClass for persistent EFI and TPM VMs with persistent EFI variables or a persistent TPM need vmStateStorageClass or a default StorageClass. In VMO pack 4.10.x, VMO Manager owns the KubeVirt resource, so set the value in the 4.9.x values before upgrading or edit it on the KubeVirt Configuration page afterward. * DOC-3299: apply verified VM state StorageClass behavior and review fixes * DOC-3299: document the VMPersistentState gate for persistent EFI and TPM --------- (cherry picked from commit 27236f5) Co-authored-by: Linus Bourque <linus@spectrocloud.com> Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com> Co-authored-by: Ben Radstone <56587332+benradstone@users.noreply.github.com>
9 of 13 tasks
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
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.
✅ Pull Request Checklist
Before submitting your PR for review, please complete this checklist to ensure quality.
Checklist
provides any additional context.
no corresponding Jira ticket, then please indicate so in this section.
makes no user-facing changes, please indicate so in this section.
Vale accept list.
This can be done later, but leave a note if required.
auto-backportlabel, as well as thebackport-version-**labels.example, Engineering, Product, etc.)
notify-slacklabel once this checklist has been completed. The team will be notified and review your PR.Good job! 👏👏👏
📝 Describe the Change
Documents what a VM with persistent firmware state needs on VMO 4.10.x: the
VMPersistentStatefeature gate and a StorageClass that supportsFilesystem.VMPersistentStategate. Without it, the wizard greys out both options and shows "Requires the VMPersistentState feature gate". The page then lists KubeVirt's StorageClass lookup order (vmStateStorageClass, theis-default-virt-classannotation, the cluster default). Secure Boot alone needs neither. The TPM row now uses the UI labels TPM Device and Persistent TPM State.VMPersistentStateon clusters upgraded from 4.9.x. Two new Parameter Mapping rows coveradditionalFeatureGatesandvmStateStorageClass. VMO Manager keeps the existingKubeVirtresource's gates and StorageClass when it takes over, and the 4.9.x values leaveVMPersistentStatecommented out, so upgraded clusters don't have it.Abirami confirmed the upgrade behavior and both ways to enable the gate: uncomment it in the 4.9.x values before the upgrade, or add it on the KubeVirt Configuration page after. The rest is verified against the VMO 4.10 source, the 4.9.9 pack values, and KubeVirt v1.8.4.
💻 Changed Pages
🎫 Jira Tickets