Reboot/Update Node in a HA-Cluster

[Ramalama]

Hey Guys, how do you reboot your nodes in a HA-Cluster?

I simply don't want that the VM's start on another node, so im disabling HA for all VM's/Containers and re-enable them after a reboot.
But this nerves with time.

Do you have any workarounds for that?

Cheers

 

[bbgeek17]

I simply don't want that the VM's start on another node, so im disabling HA for all VM's/Containers and re-enable them after a reboot.
But this nerves with time.

Have you looked at Maintenance mode settings?

---

Blockbridge : Ultra low latency all-NVME shared storage for Proxmox - https://www.blockbridge.com/proxmox

 

[Ramalama]

Have you looked at Maintenance mode settings?

---

Blockbridge : Ultra low latency all-NVME shared storage for Proxmox - https://www.blockbridge.com/proxmox

TBH, yeah, but i don't understand how i can setup it, to not migrate if i just want to reboot..

In short, migration in this case is unnecessary/makes no sense, because of multiple reasons, so i simply dont want to migrate just for a normal reboot. The vms can be offline for 5 minutes.
If a host gets terminated/powerloss or something, then its another story. Then i need HA.

This is a mini cluster, thats only for VMs inside DMZ. On the internal Proxmox Cluster, where i have 2 big genoa Servers with 768gb ram, the migration for a reboot isn't an issue.
But on the mini DMZ Cluster, there are multiple things that are limiting a bit, basically it will work, sure, it will be just stupid.
So i would simply prefer a simple reboot without migration.
I dont think im alone.
So there is surely something that i simply missed/dont know.

Cheers