Enable dynamic scaling of Kubernetes cluster offerings for KVM#13226
Enable dynamic scaling of Kubernetes cluster offerings for KVM#13226bernardodemarco wants to merge 1 commit into
Conversation
Codecov Report❌ Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## main #13226 +/- ##
============================================
+ Coverage 17.67% 18.10% +0.42%
- Complexity 15792 16749 +957
============================================
Files 5922 6037 +115
Lines 533165 542924 +9759
Branches 65208 66482 +1274
============================================
+ Hits 94242 98292 +4050
- Misses 428276 433584 +5308
- Partials 10647 11048 +401
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
|
@blueorangutan package |
|
@winterhazel a [SL] Jenkins job has been kicked to build packages. It will be bundled with no SystemVM templates. I'll keep you posted as I make progress. |
|
Packaging result [SF]: ✖️ el8 ✖️ el9 ✖️ debian ✖️ suse15. SL-JID 17998 |
|
@blueorangutan package |
|
@bernardodemarco a [SL] Jenkins job has been kicked to build packages. It will be bundled with no SystemVM templates. I'll keep you posted as I make progress. |
|
Packaging result [SF]: ✔️ el8 ✔️ el9 ✔️ el10 ✔️ debian ✔️ suse15. SL-JID 18002 |
Description
PR #12975 introduced support for live scaling VMs with fixed service offerings on KVM. However, it did not remove a constraint in the Kubernetes cluster scaling workflow that prevented changing cluster compute offerings while the clusters were running.
This PR removes this leftover constraint, enabling dynamic scaling of Kubernetes cluster offerings.
Types of changes
Feature/Enhancement Scale or Bug Severity
Feature/Enhancement Scale
Screenshots (if appropriate):
How Has This Been Tested?
Created a k8s cluster with a compute offering of 2 vCPUs and 4096 MiB of memory (without CPU cap):
k8s cluster details
Scaled the k8s cluster and upgraded its offering to 2 vCPUs and 4096 MiB of memory (with CPU cap):
k8s cluster control plane VM XML
Scaled the worker nodes compute offering to 3 vCPUs and 4096 MiB of memory (with CPU cap):
k8s cluster details
k8s cluster worker plane VM XML