[automated] Bump milvus version to v2.4.17 (#37937)

Bump milvus version to v2.4.17
Signed-off-by: sre-ci-robot sre-ci-robot@users.noreply.github.com

Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>

deployments/binary/README.md

@@ -30,7 +30,7 @@ $ ./minio server /minio
 To start Milvus standalone, you need a Milvus binary file. Currently you can get the latest version of Milvus binary file through the Milvus docker image. (We will upload Milvus binary files in the future)
 
 ```shell
-$ docker run -d --name milvus milvusdb/milvus:v2.3.0 /bin/bash
+$ docker run -d --name milvus milvusdb/milvus:v2.4.17 /bin/bash
 $ docker cp milvus:/milvus .
 ```
 

deployments/docker/cluster-distributed-deployment/inventory.ini

@@ -33,7 +33,7 @@ dependencies_network= host
 nodes_network= host
 
 ; Setup varibale to controll what image version of Milvus to use.
-image= milvusdb/milvus:v2.3.0
+image= milvusdb/milvus:v2.4.17
 
 ; Setup static IP addresses of the docker hosts as variable for container environment variable config.
 ; Before running the playbook, below 4 IP addresses need to be replaced with the IP of your host VM

deployments/docker/gpu/standalone/docker-compose.yml

@@ -38,7 +38,7 @@ services:
 
   standalone:
     container_name: milvus-standalone
-    image: milvusdb/milvus:v2.3.0-gpu
+    image: milvusdb/milvus:v2.4.17-gpu
     command: ["milvus", "run", "standalone"]
     security_opt:
       - seccomp:unconfined

deployments/docker/standalone/docker-compose.yml

@@ -38,7 +38,7 @@ services:
 
   standalone:
     container_name: milvus-standalone
-    image: milvusdb/milvus:v2.3.0
+    image: milvusdb/milvus:v2.4.17
     command: ["milvus", "run", "standalone"]
     security_opt:
     - seccomp:unconfined