Repository navigation
Commit 039b67e
feat(vm-instance): add firmware config (UEFI/BIOS, Secure Boot, persistent EFI)
Expose a per-VM `firmware` block on the VMInstance API so users can
control the boot mode directly instead of relying solely on the
instanceProfile:
- bootloader: "uefi" (OVMF) or "bios" (SeaBIOS); empty inherits the
instanceProfile default (backward compatible)
- secureBoot: enable UEFI Secure Boot (also emits domain.features.smm,
which KubeVirt requires when Secure Boot is on)
- efiPersistent: persist EFI NVRAM so enrolled Secure Boot keys (e.g. an
updated Microsoft UEFI CA) survive reboots
efiPersistent uses a KubeVirt backend-storage PVC. On the default
ReadWriteOnce storage that PVC pins the VM to its node, so a
persistent-EFI VM cannot be live-migrated; this is documented on the
field and is sufficient for one-time in-guest tasks such as a Microsoft
UEFI CA update. Live-migration would require an RWX-Filesystem
vmStateStorageClass and is out of scope for this chart.
Regenerated values.schema.json, README, the generated API types and
deepcopy, and the vm-instance-rd ApplicationDefinition.
Co-Authored-By: Claude <[email protected]>
Signed-off-by: Andrei Kvapil <[email protected]>1 parent c8e4d97 commit 039b67e
7 files changed
Lines changed: 227 additions & 164 deletions
File tree
- api/apps/v1alpha1/vminstance
- packages
- apps/vm-instance
- templates
- system/vm-instance-rd/cozyrds
Some generated files are not rendered by default. Learn more about customizing how changed files appear on GitHub.
Some generated files are not rendered by default. Learn more about customizing how changed files appear on GitHub.
0 commit comments