Skip to content

Commit

Permalink
docs: update lossy upgrade to disruptive upgrade (#1170)
Browse files Browse the repository at this point in the history
  • Loading branch information
CaitinChen authored Nov 7, 2024
1 parent f75f5d4 commit 1746a1f
Showing 1 changed file with 3 additions and 3 deletions.
6 changes: 3 additions & 3 deletions docs/en/administration/upgrade-juicefs-client.md
Original file line number Diff line number Diff line change
Expand Up @@ -13,14 +13,14 @@ In fact, upgrading [JuiceFS CSI Driver](./upgrade-csi-driver.md) will also upgra
Currently, there are two methods for upgrading Mount Pod container images:

- [Smooth upgrade of Mount Pods](#smooth-upgrade): This method allows you to upgrade an already created Mount Pod without rebuilding the application Pod.
- [Lossy upgrade of Mount Pods](../guide/custom-image.md#overwrite-mount-pod-image): This method requires rebuilding the application Pod to upgrade an existing Mount Pod.
- [Disruptive upgrade of Mount Pods](../guide/custom-image.md#overwrite-mount-pod-image): This method requires rebuilding the application Pod to upgrade an existing Mount Pod.

Refer to [this document](../guide/custom-image.md#ce-ee-separation) to find the tag for the latest Mount Pod container image in Docker Hub. Then, choose the appropriate upgrade method based on your CSI Driver version and the mount mode you are using:

| | Version 0.25.0 and above | Version before 0.25.0 |
|:------------------:|:------------------------:|:-----------------------:|
| **Mount Pod mode** | Smooth upgrade of Mount Pods | Lossy upgrade of Mount Pods |
| **Sidecar mode** | Lossy upgrade of Mount Pods | Lossy upgrade of Mount Pods |
| **Mount Pod mode** | Smooth upgrade of Mount Pods | Disruptive upgrade of Mount Pods |
| **Sidecar mode** | Disruptive upgrade of Mount Pods | Disruptive upgrade of Mount Pods |

**Note:** After overwriting the Mount Pod image, further CSI Driver upgrades will no longer automatically update the Mount Pod image.

Expand Down

0 comments on commit 1746a1f

Please sign in to comment.