Hey guys,
today in one of our standup meetings we thought about improving out update strategy. Currently we run multiple clusters running on different versions of Proxmox. So far, to ensure we have our HA services always running, we update one cluster at a time, let it run to ensure its stable and roughly a month later its counterpart.
We do have development clusters in place to test the most recent Proxmox changes but we can never assure the exact software version on each cluster we tested.
What we are looking for is a historically saved set/version for all incoming Proxmox updates (like "Update-Packages"), to ensure if you update a machine you can update it to a SPECIFIC set of packages. Like if we tested the "most recent version" from 01. January 2025 on our Dev cluster, it looks good, we want to run THIS version on our live-clusters a month later.
How do you guys approach this? I am really looking forward to find ideas and solutions to that.
Florian
today in one of our standup meetings we thought about improving out update strategy. Currently we run multiple clusters running on different versions of Proxmox. So far, to ensure we have our HA services always running, we update one cluster at a time, let it run to ensure its stable and roughly a month later its counterpart.
We do have development clusters in place to test the most recent Proxmox changes but we can never assure the exact software version on each cluster we tested.
What we are looking for is a historically saved set/version for all incoming Proxmox updates (like "Update-Packages"), to ensure if you update a machine you can update it to a SPECIFIC set of packages. Like if we tested the "most recent version" from 01. January 2025 on our Dev cluster, it looks good, we want to run THIS version on our live-clusters a month later.
How do you guys approach this? I am really looking forward to find ideas and solutions to that.
Florian
Last edited: