Auto-update blog content from Obsidian: 2025-11-02 08:44:06
All checks were successful
Blog Deployment / Check-Rebuild (push) Successful in 6s
Blog Deployment / Build (push) Has been skipped
Blog Deployment / Deploy-Staging (push) Successful in 11s
Blog Deployment / Test-Staging (push) Successful in 2s
Blog Deployment / Merge (push) Successful in 7s
Blog Deployment / Deploy-Production (push) Successful in 10s
Blog Deployment / Test-Production (push) Successful in 2s
Blog Deployment / Clean (push) Has been skipped
Blog Deployment / Notify (push) Successful in 2s

This commit is contained in:
Gitea Actions
2025-11-02 08:44:06 +00:00
parent 62833b288a
commit 58856f4668

View File

@@ -26,9 +26,14 @@ In this article, I will walk you through the upgrade steps for my Proxmox VE HA
Before jumping into the upgrade, let's review the prerequisites: Before jumping into the upgrade, let's review the prerequisites:
- All nodes upgraded to the latest version of Proxmox VE 8.4. 1. All nodes upgraded to the latest version of Proxmox VE 8.4.
Ensure your node(s) have correct package repository configuration (web UI, Node -> Repositories) if your pve-manager version isn't at least `8.4.1`. The latest version for Proxmox VE 8 is `8.4.1`. My nodes are currently in version 8.3.2, hence a first update is necessary before the major upgrade.
2.
nsure your node(s) have correct package repository configuration (web UI, Node -> Repositories) if your pve-manager version isn't at least `8.4.1`.
- Hyper-converged Ceph: upgrade any Ceph Quincy or Ceph Reef cluster to Ceph 19.2 Squid **before** you start the Proxmox VE upgrade to 9.0. - Hyper-converged Ceph: upgrade any Ceph Quincy or Ceph Reef cluster to Ceph 19.2 Squid **before** you start the Proxmox VE upgrade to 9.0.