flux: re-enable KubeVirt + CDI (new 16GB Proxmox nodes with nested virt)

Co-Authored-By: Claude Opus 4.8 <[email protected]>

platform-config/kustomization.yaml

@@ -35,11 +35,11 @@ resources:
   # operators register; the ServiceMonitors/alerts consume monitoring.coreos.com. All CRs of platform-
   # installed CRDs -> applied here, gated dependsOn platform (F-MON1). The dashboard is a plain
   # ConfigMap kept beside them for locality.
-  # TEMP-DISABLED (memory): - ../platform/kubevirt/kubevirt-cr.yaml
-  # TEMP-DISABLED (memory): - ../platform/kubevirt/cdi-cr.yaml
-  # TEMP-DISABLED (memory): - ../platform/kubevirt/servicemonitor.yaml
-  # TEMP-DISABLED (memory): - ../platform/kubevirt/alerts.yaml
-  # TEMP-DISABLED (memory): - ../platform/kubevirt/dashboard.yaml
+  - ../platform/kubevirt/kubevirt-cr.yaml
+  - ../platform/kubevirt/cdi-cr.yaml
+  - ../platform/kubevirt/servicemonitor.yaml
+  - ../platform/kubevirt/alerts.yaml
+  - ../platform/kubevirt/dashboard.yaml
   # --- Phase 6 — Identity / SSO (ADR-0014) ---
   # keycloak: the CNPG DB Cluster + Keycloak instance + realm import (CRs of the CNPG / Keycloak
   # operator CRDs installed by platform/cnpg + platform/keycloak) + its ingress + ServiceMonitor.

platform/kustomization.yaml

@@ -36,5 +36,4 @@ 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). ----
-  # TEMP-DISABLED (memory relief; KubeVirt conformance already certified — re-enable when RAM grows):
-  # - kubevirt           # KubeVirt + CDI operators (register kubevirt.io / cdi.kubevirt.io CRDs)
+  - kubevirt           # KubeVirt + CDI operators (register kubevirt.io / cdi.kubevirt.io CRDs)