VEP 280: Expose Instancetype Resources in VirtualMachine Status#281
Open
lyarwood wants to merge 1 commit intokubevirt:mainfrom
Open
VEP 280: Expose Instancetype Resources in VirtualMachine Status#281lyarwood wants to merge 1 commit intokubevirt:mainfrom
lyarwood wants to merge 1 commit intokubevirt:mainfrom
Conversation
kubevirt-bot
added
the
dco-signoff: yes
|
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: The full list of commands accepted by this bot can be found here. DetailsNeeds approval from an approver in each of these files:Approvers can indicate their approval by writing |
lyarwood
changed the title
This was referenced Apr 20, 2026
lyarwood
moved this to Proposed for consideration
in KubeVirt 1.9 Enhancements Tracking
Member
|
/cc |
0xFelix
reviewed
Apr 23, 2026
lyarwood
force-pushed
the
vep-278-instancetype-status-resources
branch
from
f8f2703 to
5ac223d
Compare
This adds a new VEP proposing the addition of a `resources` field to `vm.status.instancetypeRef` that exposes the resolved CPU topology (cores, sockets, threads) and guest memory from a referenced instancetype. Assisted-By: Claude <noreply@anthropic.com> Signed-off-by: Lee Yarwood <lyarwood@redhat.com>
lyarwood
force-pushed
the
vep-278-instancetype-status-resources
branch
from
5ac223d to
3db6ffa
Compare
0xFelix
reviewed
Apr 27, 2026
Member
0xFelix
left a comment
0xFelix
left a comment
There was a problem hiding this comment.
Last question: Did you explore the use of expand-spec, is it absolutely no option?
|
|
||
| ```yaml | ||
| # Before: u1.medium (1 socket, 4Gi) | ||
| # After: u1.large (2 sockets, 8Gi) |
Member
There was a problem hiding this comment.
Instancetypes alone do not provide sockets, they provide vCPUs?
Member
Author
There was a problem hiding this comment.
By default exposed as sockets without a provided preference.
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.
VEP Metadata
Tracking issue: #280
SIG label: /sig compute
What this PR does
Introduces VEP 280, proposing the addition of a
resourcesfield tovm.status.instancetypeRefthat exposes the resolved CPU topology (cores, sockets, threads) and guest memory from a referenced instancetype.This allows users and tooling to see the guest-visible resources provided by an instancetype directly in the VirtualMachine status without needing to start the VM, fetch the instancetype object, or call expand-spec.
Implementation PR: kubevirt/kubevirt#16130
Special notes for your reviewer
This is a read-only status field addition with no behavioral changes, so no feature gate is proposed.