Skip to content

kb: Add "Batch updating the Overcommit CPU & Memory settings to exist… #89

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
pfischbacher wants to merge 3 commits into
base: main
Choose a base branch
from
Open

kb: Add "Batch updating the Overcommit CPU & Memory settings to exist… #89

Changes from all commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
51667c9
kb: Add "Batch updating the Overcommit CPU & Memory settings to exist…
pfischbacher Sep 25, 2025
33b24b5
added slug and updated file naming format.
pfischbacher Nov 10, 2025
c04ae10
added slug and updated file naming format.
pfischbacher Nov 10, 2025
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
19 changes: 19 additions & 0 deletions kb/2025-09-25/update_overcommit_cpu_memory.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -0,0 +1,19 @@
---
title: 'CPU and Memory Overcommit settings not being applied to existing VMs'
description: 'Batch update the CPU and Memory Overcommit settings to existing VMs in Harvester.'
slug: update_overcommit_cpu_memory
authors:
- name: Philip Fischbacher
title: Support Engineer
url: https://github.com/pfischbacher
image_url: https://github.com/pfischbacher.png
tags: [settings, overcommit, cpu, memory]
hide_table_of_contents: false
---
Users may wish to have their most recent modifications to the Overcommit settings applied to all their existing Harvester VMs.

However, Harvester’s CPU/Memory overcommit settings only affect scheduling and resource allocation for new VMs, existing VMs keep the resource limits and requests that were set when they were created. The VM spec isn’t automatically updated when cluster-level defaults change, so you must edit or recreate the VM to apply new overcommit values.

You can use the following script to update ALL your exisiting Harvester VMs in a single Harvester cluster to have the updated CPU and Memory Overcommit settings. This script will not update the Storage overcommit settings.

[Harvester batch update script](https://github.com/pfischbacher/harvester-overcommit-update-script)