Milvus 2.2.3 supports rolling update. This script helps you to perform a rolling update with zero downtime.
Note:
- Milvus version must be after 2.2.0.
- This script only applies to update Milvus installed with Helm and does not apply to Milvus installed with Milvus Operator.
- This script only supports update operation now.
- Rolling update is not supported in Milvus standalone with RocksMQ.
Parameters | Description | Default value | Required |
---|---|---|---|
i |
The Milvus instance name. | None |
True |
n |
The namespace that Milvus is installed in. | default |
False |
t |
The target Milvus version. | None |
True |
w |
The new Milvus image tag. | milvusdb/milvus:v2.2.3 |
True |
o |
The operation. | update |
False |
- Check all deployments of the Milvus instance. Make sure no deployment is blocked.
- Update the deployments one by one. The update order is hard-coded for now.
- Specify the namespace, Milvus instance name, target Milvus version, and target image in the script.
- Run the script. The following script updates Milvus to 2.2.3.
sh rollingUpdate.sh -n default -i my-release -o update -t 2.2.3 -w 'milvusdb/milvus:v2.2.3'
Note
- This script update the deployment by
kubectl patch
and watch the deployment's status bykubectl rollout status
.- The
target version
is the deployment's labelapp.kubernetes.io/version
and is updated bykubectl patch
.