diff --git a/docs/Virtualisation/pve-k8s-ceph-config.md b/docs/Virtualisation/pve-k8s-ceph-config.md index 0e1b5e5..f0dcd12 100644 --- a/docs/Virtualisation/pve-k8s-ceph-config.md +++ b/docs/Virtualisation/pve-k8s-ceph-config.md @@ -60,7 +60,7 @@ Add **persistent static routes** on **all PVE Ceph hosts** to allow Ceph to send ```ini # Example: post-up ip route add via dev - # e.g., post-up ip route add 10.1.0.0/16 via 172.30.100.41 dev vmbr0 + # e.g., post-up ip route add 10.1.0.0/16 via 172.35.100.40 dev vmbr0 ``` ### C. K8s Node IP Forwarding (Gateway Function) @@ -86,29 +86,29 @@ This routing is **only required** if the **Ceph Public Network** (the network Ce ethernets: eth0: # Replace with your primary K8s network interface routes: - # Route 1: Directs traffic destined for the first Ceph Monitor IP (10.15.16.1) - # through three different PVE hosts (172.30.25.x) as gateways. + # Route 1: Directs traffic destined for the first Ceph Monitor IP (10.11.12.1) + # through three different PVE hosts (172.35.100.x) as gateways. # The lowest metric (10) is preferred. - - to: 10.15.16.1/32 - via: 172.30.25.10 + - to: 10.11.12.1/32 + via: 172.35.100.10 metric: 10 - - to: 10.15.16.1/32 - via: 172.30.25.20 + - to: 10.11.12.1/32 + via: 172.35.100.20 metric: 100 - - to: 10.15.16.1/32 - via: 172.30.25.30 + - to: 10.11.12.1/32 + via: 172.35.100.30 metric: 100 - # Route 2: Directs traffic destined for the second Ceph Monitor IP (10.15.16.2) + # Route 2: Directs traffic destined for the second Ceph Monitor IP (10.11.12.2) # with a similar failover strategy. - - to: 10.15.16.2/32 - via: 172.30.25.20 + - to: 10.11.12.2/32 + via: 172.35.100.20 metric: 10 - - to: 10.15.16.2/32 - via: 172.30.25.10 + - to: 10.11.12.2/32 + via: 172.35.100.10 metric: 100 - - to: 10.15.16.2/32 - via: 172.30.25.30 + - to: 10.11.12.2/32 + via: 172.35.100.30 metric: 100 ``` @@ -116,7 +116,9 @@ Use route priorities (Lower is Higher) to prefer the most direct path, while sti --- -## 4. 🧩 MicroK8s CSI Driver Configuration (The Path Fix) +## 4. 🧩 MicroK8s CSI Driver Configuration (The Path Fix) - Conditional/Advanced ⚠️ + +This adjustment is **only required** if **MicroK8s** is running your Kuberneted deployment. **Alternative changes** may be needed for other Kubetnetes distributions. This resolves the **`staging path does not exist on node`** error for the Node Plugin.