Owner directive: PVE runs only the three k8s VMs. This removes every repo reference to the decommissioned guests (proxmox-dns trio lxc 118/218/318, rustfs trio lxc 800/801/802, fortress vm 102, paperless vm 111) — 726 deletions across 17 files:
opentofu: the three guest .tf files plus backup_jobs.tf — the nightly vzdump job covered ONLY destroyed guests (k8s VMs are deliberately excluded; their data protection is Velero/CNPG). The next tofu apply drops the orphaned backup job from PVE and reconciles state for the destroyed guests (same flow as #232).
ansible: roles/proxmox-dns, both install plays, check-chaos-testing.yml (failover tests for decommissioned DNS-HA/postgres LXCs), the proxmox-dns and rustfs vault files, and the [proxmox_dns_ha] inventory group.
monitoring: the dns-servers scrape job in both the k8s HelmRelease and the legacy prometheus-server template — after Flux reconciles, the TargetDown (dns-servers) alert resolves.
Guest destruction on PVE is pending on the owner (classifier blocked my pct/qm destroy; exact commands provided in chat). Template vm 605 kept — it is the tofu-managed clone source for the k8s VMs.
Known remaining rot, deliberately out of scope (flagging for a follow-up): pve_hosts.yml still lists authentik-db/app LXCs and grafana.srv, all long gone; several legacy ansible roles (prometheus-server etc.) target hosts that no longer exist.
Owner directive: **PVE runs only the three k8s VMs.** This removes every repo reference to the decommissioned guests (proxmox-dns trio lxc 118/218/318, rustfs trio lxc 800/801/802, fortress vm 102, paperless vm 111) — 726 deletions across 17 files:
- **opentofu**: the three guest .tf files plus `backup_jobs.tf` — the nightly vzdump job covered ONLY destroyed guests (k8s VMs are deliberately excluded; their data protection is Velero/CNPG). The next `tofu apply` drops the orphaned backup job from PVE and reconciles state for the destroyed guests (same flow as #232).
- **ansible**: `roles/proxmox-dns`, both install plays, `check-chaos-testing.yml` (failover tests for decommissioned DNS-HA/postgres LXCs), the proxmox-dns and rustfs vault files, and the `[proxmox_dns_ha]` inventory group.
- **monitoring**: the `dns-servers` scrape job in both the k8s HelmRelease and the legacy prometheus-server template — after Flux reconciles, the TargetDown (dns-servers) alert resolves.
**Guest destruction on PVE** is pending on the owner (classifier blocked my `pct/qm destroy`; exact commands provided in chat). Template vm 605 kept — it is the tofu-managed clone source for the k8s VMs.
**Known remaining rot, deliberately out of scope** (flagging for a follow-up): `pve_hosts.yml` still lists authentik-db/app LXCs and grafana.srv, all long gone; several legacy ansible roles (prometheus-server etc.) target hosts that no longer exist.
Closes #259
🤖 Generated with [Claude Code](https://claude.com/claude-code)
https://claude.ai/code/session_01NV7bZzZLeoFUEdAeCSLEei
Owner directive: PVE runs ONLY the three k8s VMs. The proxmox-dns trio
(lxc 118/218/318), rustfs trio (lxc 800/801/802), fortress (vm 102)
and paperless (vm 111) are decommissioned; guest definitions are being
destroyed on PVE out-of-band.
Removed:
- opentofu: lxc_118_proxmox_dns.tf, vm_102_fortress.tf,
vm_111_paperless.tf, backup_jobs.tf (the vzdump job covered ONLY
destroyed guests — next tofu apply removes the job from PVE; k8s
data protection is Velero/CNPG)
- ansible: roles/proxmox-dns, install-proxmox-dns{,-ha}.yml,
check-chaos-testing.yml (tested failover of decommissioned DNS-HA
and postgres LXCs), proxmox_dns_vault.yml, rustfs_vault.yml,
[proxmox_dns_ha] inventory group
- monitoring: dns-servers scrape job in both the k8s HelmRelease and
the legacy prometheus-server template — resolves TargetDown
(dns-servers)
Closes#259
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01NV7bZzZLeoFUEdAeCSLEei
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Owner directive: PVE runs only the three k8s VMs. This removes every repo reference to the decommissioned guests (proxmox-dns trio lxc 118/218/318, rustfs trio lxc 800/801/802, fortress vm 102, paperless vm 111) — 726 deletions across 17 files:
backup_jobs.tf— the nightly vzdump job covered ONLY destroyed guests (k8s VMs are deliberately excluded; their data protection is Velero/CNPG). The nexttofu applydrops the orphaned backup job from PVE and reconciles state for the destroyed guests (same flow as #232).roles/proxmox-dns, both install plays,check-chaos-testing.yml(failover tests for decommissioned DNS-HA/postgres LXCs), the proxmox-dns and rustfs vault files, and the[proxmox_dns_ha]inventory group.dns-serversscrape job in both the k8s HelmRelease and the legacy prometheus-server template — after Flux reconciles, the TargetDown (dns-servers) alert resolves.Guest destruction on PVE is pending on the owner (classifier blocked my
pct/qm destroy; exact commands provided in chat). Template vm 605 kept — it is the tofu-managed clone source for the k8s VMs.Known remaining rot, deliberately out of scope (flagging for a follow-up):
pve_hosts.ymlstill lists authentik-db/app LXCs and grafana.srv, all long gone; several legacy ansible roles (prometheus-server etc.) target hosts that no longer exist.Closes #259
🤖 Generated with Claude Code
https://claude.ai/code/session_01NV7bZzZLeoFUEdAeCSLEei
Owner directive: PVE runs ONLY the three k8s VMs. The proxmox-dns trio (lxc 118/218/318), rustfs trio (lxc 800/801/802), fortress (vm 102) and paperless (vm 111) are decommissioned; guest definitions are being destroyed on PVE out-of-band. Removed: - opentofu: lxc_118_proxmox_dns.tf, vm_102_fortress.tf, vm_111_paperless.tf, backup_jobs.tf (the vzdump job covered ONLY destroyed guests — next tofu apply removes the job from PVE; k8s data protection is Velero/CNPG) - ansible: roles/proxmox-dns, install-proxmox-dns{,-ha}.yml, check-chaos-testing.yml (tested failover of decommissioned DNS-HA and postgres LXCs), proxmox_dns_vault.yml, rustfs_vault.yml, [proxmox_dns_ha] inventory group - monitoring: dns-servers scrape job in both the k8s HelmRelease and the legacy prometheus-server template — resolves TargetDown (dns-servers) Closes #259 Co-Authored-By: Claude Fable 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01NV7bZzZLeoFUEdAeCSLEei