Real-time monitoring dashboard for Proxmox VE, PBS, Docker, Kubernetes, TrueNAS and vSphere. Self-hosted, with alerts for failed backups, full disks, unhealthy containers and offline nodes.
Go aialertsdashboarddockerdocker-monitoringgohomelabinfrastructure-monitoringkubernetesmonitoringmspproxmoxproxmox-backup-serverproxmox-mail-gatewayproxmox-veself-hostedtruenastypescriptvspherewebhooks
Preserve read-only container-ID checks in the install contract
pulse-triage[bot]de4d52f42bbb
diff --git a/docs/release-control/v6/internal/subsystems/deployment-installability.md b/docs/release-control/v6/internal/subsystems/deployment-installability.mdindex af4ff6b71c..c1142ae3f6 100644--- a/docs/release-control/v6/internal/subsystems/deployment-installability.md+++ b/docs/release-control/v6/internal/subsystems/deployment-installability.md@@ -849,9 +849,11 @@ payload admission and scoped install/update behaviour are unchanged.no implicit legacy-cleanup implementation. The real `create_lxc_container`entry is exercised through a controlling-terminal Cancel, Quick and Advancedselection and a detached noninteractive Quick entry, with every Proxmox action-an inert fixture. No existing-guest inventory/lifecycle action may precede the-first configuration prompt; Cancel must complete without one. The separate-legacy cleanup safety suite continues to own its explicit maintenance path.+an inert fixture. The selected-ID lookup remains read-only. No implicit legacy+cleanup or guest lifecycle action may precede the first configuration prompt;+Cancel must complete without Proxmox actions. Normal read-only ID collision+checks are unchanged. The separate legacy cleanup safety suite continues to own+its explicit maintenance path.### Legacy credential cleanup needs complete inventory and preserved keys