Skip to content

Added memoryOvercommit configuration as yaml specification similar to cpu over commit configuration#981

Open
shubhamrajvanshi wants to merge 1 commit intokubevirt:mainfrom
shubhamrajvanshi:patch-3
Open

Added memoryOvercommit configuration as yaml specification similar to cpu over commit configuration#981
shubhamrajvanshi wants to merge 1 commit intokubevirt:mainfrom
shubhamrajvanshi:patch-3

Conversation

@shubhamrajvanshi
Copy link
Copy Markdown
Contributor

@shubhamrajvanshi shubhamrajvanshi commented Mar 19, 2026

Added memoryOvercommit configuration as yaml specification similar to cpu over commit configuration

What this PR does / why we need it:

Which issue(s) this PR fixes (optional, in fixes #<issue number>(, fixes #<issue_number>, ...) format, will close the issue(s) when PR gets merged):
Fixes #

Special notes for your reviewer:

Checklist

This checklist is not enforcing, but it's a reminder of items that could be relevant to every PR.
Approvers are expected to review this list.

Release note:


Added memoryOvercommit configuration as yaml specification similar to cpu over commit configuration

Signed-off-by: Shubham Rajvanshi <shubham@spectrocloud.com>
@kubevirt-bot kubevirt-bot added the dco-signoff: yes Indicates the PR's author has DCO signed all their commits. label Mar 19, 2026
@kubevirt-bot kubevirt-bot added the needs-ok-to-test Indicates a PR that requires an org member to verify it is safe to test. label Mar 19, 2026
@kubevirt-bot
Copy link
Copy Markdown
Contributor

Hi @shubhamrajvanshi. Thanks for your PR.

I'm waiting for a kubevirt member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work.

Regular contributors should join the org to skip this step.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

I understand the commands that are listed here.

Details

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.

@shubhamrajvanshi shubhamrajvanshi changed the title Update node_overcommit.md Added memoryOvercommit configuration as yaml specification similar to cpu over commit configuration Mar 19, 2026
@jean-edouard
Copy link
Copy Markdown
Contributor

/cc

Copy link
Copy Markdown
Contributor

@jean-edouard jean-edouard left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

/approve

@kubevirt-bot
Copy link
Copy Markdown
Contributor

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: jean-edouard

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Details Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@kubevirt-bot kubevirt-bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Apr 17, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

approved Indicates a PR has been approved by an approver from all required OWNERS files. dco-signoff: yes Indicates the PR's author has DCO signed all their commits. needs-ok-to-test Indicates a PR that requires an org member to verify it is safe to test. size/S

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants