Skip to content

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

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
shubhamrajvanshi wants to merge 1 commit into
base: main
Choose a base branch
from
Open

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

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
11 changes: 10 additions & 1 deletion docs/compute/node_overcommit.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -94,7 +94,16 @@ VMI in case the node gets under memory pressure.
Implicit memory overcommit is disabled by default. This means that when
memory request is not specified, it is set to match
`spec.domain.memory.guest`. However, it can be enabled using
`spec.configuration.developerConfiguration.memoryOvercommit` in the `kubevirt` CR. For example, by setting

```yaml
...
spec:
configuration:
developerConfiguration:
memoryOvercommit: 150
```

in the `kubevirt` CR. For example, by setting
`memoryOvercommit: "150"` we define that when memory request is not
explicitly set, it will be implicitly set to achieve memory overcommit
of 150%. For instance, when `spec.domain.memory.guest: 3072M`, memory
Expand Down