Mid-migration made the new architecture look worse because the overhead arrived before the benefits did.
Original work date
June
The problem
During the bare-metal Docker to Proxmox plus k3s migration, the resource picture looked ugly. Proxmox added overhead. Ceph added overhead. VMs had fixed allocations. The old Docker hosts still existed. Workloads had not fully moved into k3s yet. So for a while, the new platform looked like a regression.
The environment
- App: Proxmox / Ceph / k3s
- Host: Nahida, Furina, Venti
- Cluster / namespace:
- Version:
- Relevant config:
What failed
That was the ugly middle. Nahida was carrying old Thoma workload, Furina was carrying old Kaveh workload, and Venti had room that the old architecture was not really using yet.
The fix
The architecture only started making sense once the apps moved into k3s, old Docker VMs could be decommissioned, and workloads could spread across the cluster.
Final state
What I learned
The middle of a migration is where everything costs more and nothing feels better yet.
Useful commands / config
paste commands here