Skip to content

Commit ad5463f

Browse files
authored
Merge pull request #3269 from liyun95/preview
update 2.6.0 upgrade guide
2 parents 6fc9216 + 529f322 commit ad5463f

File tree

2 files changed

+15
-21
lines changed

2 files changed

+15
-21
lines changed

site/en/Variables.json

Lines changed: 2 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -20,5 +20,6 @@
2020
"milvus_image": "2.4.1",
2121
"attu_release": "2.3.10",
2222
"milvus_backup_release": "0.4.15",
23-
"birdwatcher_release": "1.0.3"
23+
"birdwatcher_release": "1.0.3",
24+
"minio_release": "RELEASE.2024-12-18T13-15-44Z"
2425
}

site/en/adminGuide/upgrade_milvus_standalone-docker.md

Lines changed: 13 additions & 20 deletions
Original file line numberDiff line numberDiff line change
@@ -40,62 +40,55 @@ This upgrade is <strong>irreversible</strong>. You cannot roll back to a previou
4040

4141
<div class="alter note">
4242

43-
Due to security concerns, Milvus upgrades its MinIO to RELEASE.2023-03-20T20-16-18Z with the release of v2.2.5. Before any upgrades from previous Milvus Standalone releases installed using Docker Compose, you should create a Single-Node Single-Drive MinIO deployment and migrate existing MinIO settings and content to the new deployment. For details, refer to [this guide](https://min.io/docs/minio/linux/operations/install-deploy-manage/migrate-fs-gateway.html#id2).
43+
Due to security concerns, Milvus upgrades its MinIO to {{var.minio_release}} with the release of v{{var.milvus_release_version}}. Before any upgrades from previous Milvus Standalone releases installed using Docker Compose, you should create a Single-Node Single-Drive MinIO deployment and migrate existing MinIO settings and content to the new deployment. For details, refer to [this guide](https://min.io/docs/minio/linux/operations/install-deploy-manage/migrate-fs-gateway.html#id2).
4444

4545
</div>
4646

4747
## Upgrade process
4848

49-
### Step 1: Download updated Docker Compose files
50-
51-
Before upgrading, download the latest Docker Compose configuration files:
52-
53-
```bash
54-
# Download the latest docker-compose.yaml
55-
wget https://github.com/milvus-io/milvus/releases/download/v{{var.milvus_release_tag}}/milvus-standalone-docker-compose.yml -O docker-compose.yaml
56-
```
49+
### Step 1: Upgrade to v2.5.16
5750

5851
<div class="alert note">
59-
Always download the latest configuration files to ensure compatibility with the new version and access to new features.
60-
</div>
61-
62-
### Step 2: Upgrade to v2.5.16
63-
64-
<div class="alert-note">
6552

6653
Skip this step if your standalone deployment is already running v2.5.16 or higher.
6754

6855
</div>
6956

70-
1. Update the Milvus image tag in your `docker-compose.yaml` to v2.5.16:
57+
1. Edit your existing `docker-compose.yaml` file and update the Milvus image tag to v2.5.16:
7158

7259
```yaml
7360
...
7461
standalone:
7562
container_name: milvus-standalone
7663
image: milvusdb/milvus:v2.5.16
64+
...
7765
```
7866

79-
2. Apply the upgrade:
67+
2. Apply the upgrade to v2.5.16:
8068

8169
```bash
8270
docker compose down
8371
docker compose up -d
8472
```
8573

86-
3. Verify the upgrade:
74+
3. Verify the v2.5.16 upgrade:
8775

8876
```bash
8977
docker compose ps
9078
```
9179

92-
### Step 3: Upgrade to v{{var.milvus_release_version}}
80+
### Step 2: Upgrade to v{{var.milvus_release_version}}
9381

9482
Once v2.5.16 is running successfully, upgrade to v{{var.milvus_release_version}}:
9583

96-
1. Update the Milvus image tag in your `docker-compose.yaml`:
84+
1. Edit your existing `docker-compose.yaml` file and update both the Milvus and MinIO image tags:
9785

9886
```yaml
87+
...
88+
minio:
89+
container_name: milvus-minio
90+
image: minio/minio:{{var.minio_release}}
91+
9992
...
10093
standalone:
10194
container_name: milvus-standalone

0 commit comments

Comments
 (0)