Conversation
This was referenced Sep 25, 2026
coulof
force-pushed
the
feat/vm-catalog
branch
from
September 28, 2026 16:39
4a58d33 to
135acaf
Compare
Signed-off-by: coulof <florian.coulombel@suse.com>
coulof
force-pushed
the
feat/vm-catalog
branch
from
September 29, 2026 08:54
135acaf to
81380b9
Compare
coulof
marked this pull request as ready for review
September 30, 2026 14:01
This branch has not been deployed
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.
Problem:
Provisioning standard VMs currently requires manually configuring CPU, memory, disks, networks, and OS settings through the full VM creation form (as discussed in harvester/harvester#11101). With the introduction of the optional VM Catalog add-on, comprehensive documentation is needed.
Solution:
Add
docs/vm/vm-catalog.mddocumenting the new VM Catalog workflow:VirtualMachineClusterPreferenceandVirtualMachineClusterInstancetype) rather than custom Harvester catalog CRDs, delegating resolution to KubeVirt's nativeexpand-vm-specsubresource API.vm-catalogadd-on is enabled under Advanced > Addons.u1,o1,cx1,m1,n1,rt1) and size tiers.instancetype.kubevirt.io/default-preference,instancetype.kubevirt.io/default-instancetype,harvesterhci.io/os-type), recommended Linux distributions, and air-gapped staging with Hauler.Related Issue(s):
harvester/harvester#11101
Related PRs:
Test plan:
AI Usage Disclosure
Author Acknowledgments