Home-Network/home-network-k3s-impl
2
0 Fork 0
Code Issues 3 Pull Requests 2 Actions Packages Projects Releases Wiki Activity

chore(memory): temp-disable KubeVirt to relieve node memory pressure

Browse Source 
The 3x 6GB nodes are OOM (k3s-dev-2's kubelet stopped; dev-1/dev-3 <600MB free). KubeVirt runs
a full control plane (~1.5-2GB) for ZERO running VMs — its IaaS conformance (R-PLAT-03/04,
R-NET-01, R-STATE-01) is already certified, so disabling the running pods loses no delivered
capability. Re-enable (uncomment kubevirt in platform + platform-config) once the VMs' RAM is
grown. Manifests retained; reversible.
This commit is contained in:
jakman85 committed 2026-08-25 09:29:29 -05:00
1 parent c16e0889fd
commit 971c730400
2 files changed
+7 -6
Download Patch File Download Diff File Expand all files Collapse all files

No files matched your search

platform/kustomization.yaml
+2 -1
View File
@@ -37,4 +37,5 @@ resources:
# - image-automation # Phase 4 (Automated updates): Flux image-automation + Renovate
# ---- Phase 5 — IaaS proof (KubeVirt): operator CONTROLLERS only; the KubeVirt/CDI CRs +
# ServiceMonitors/alerts/dashboard are applied by platform-config (dependsOn platform, F-MON1). ----
- kubevirt # KubeVirt + CDI operators (register kubevirt.io / cdi.kubevirt.io CRDs)
# TEMP-DISABLED (memory relief; KubeVirt conformance already certified — re-enable when RAM grows):
# - kubevirt # KubeVirt + CDI operators (register kubevirt.io / cdi.kubevirt.io CRDs)