#ProxPatch for #Proxmox VE Clusters!

Automate the most repetitive operational task in Proxmox: keeping cluster nodes updated! ProxPatch drains, migrates, patches, and reboots nodes in a controlled rolling fashion — no downtime, no manual intervention.

ProxPatch is written in Rust and fully #opensource.

Website: https://proxpatch.de
GitHub: https://github.com/gyptazy/ProxPatch

#PVE #homelab #enterprise #Debian #PatchManagement #ProxmoxVE #Security #ProxLB #SecurityUpdateManagement #Automation #Rustlang

#ProxPatch for #Proxmox VE Clusters!

Automate the most repetitive operational task in Proxmox: keeping cluster nodes updated! ProxPatch drains, migrates, patches, and reboots nodes in a controlled rolling fashion — no downtime, no manual intervention.

ProxPatch is written in Rust and fully #opensource.

Website: https://proxpatch.de
GitHub: https://github.com/gyptazy/ProxPatch

#PVE #homelab #enterprise #Debian #PatchManagement #ProxmoxVE #Security #ProxLB #SecurityUpdateManagement #Automation #Rustlang

Hey #Proxmox community! I would like to hear your thoughts on how you usually update your Proxmox nodes and clusters. How do you handle minor Proxmox and #Debian package upgrades with #APT?

What would you think about a new API endpoint that lets you run unattended upgrades with a simple call like:

/nodes/{node_name}/apt/upgrade

At the moment you need to use the node’s HTML5 console to perform upgrades. Other methods exist such as running unattended Debian upgrade scripts, using patch management tools like #Spacewalk or #QualvoSec, or automating the process with #Ansible over SSH. My idea is to have an API based solution that relies on Proxmox authentication and authorization. This would also allow third party tools such as #ProxLB to provide automated patch management and even handle guest rebalancing in a way that is similar to DRS without requiring direct SSH access.
I have already been running this approach on several internal clusters since the release of PVE 8 without issues. Now I am interested to hear if you would use unattended upgrades in general or if you are already running them today.

#Linux #OpenSource #PatchManagement #Security #DevOps #Automation #Ansible #PVE #PVE8 #PVE9

Hey #Proxmox community! I would like to hear your thoughts on how you usually update your Proxmox nodes and clusters. How do you handle minor Proxmox and #Debian package upgrades with #APT?

What would you think about a new API endpoint that lets you run unattended upgrades with a simple call like:

/nodes/{node_name}/apt/upgrade

At the moment you need to use the node’s HTML5 console to perform upgrades. Other methods exist such as running unattended Debian upgrade scripts, using patch management tools like #Spacewalk or #QualvoSec, or automating the process with #Ansible over SSH. My idea is to have an API based solution that relies on Proxmox authentication and authorization. This would also allow third party tools such as #ProxLB to provide automated patch management and even handle guest rebalancing in a way that is similar to DRS without requiring direct SSH access.
I have already been running this approach on several internal clusters since the release of PVE 8 without issues. Now I am interested to hear if you would use unattended upgrades in general or if you are already running them today.

#Linux #OpenSource #PatchManagement #Security #DevOps #Automation #Ansible #PVE #PVE8 #PVE9