Milvus
Zilliz
Home
  • Administration Guide
Milvus OperatorHelmDocker Compose

Upgrade Milvus Standalone with Helm Chart

This guide describes how to upgrade your Milvus standalone deployment from v2.5.x to v2.6.0 using Helm Chart.

Before you start

What’s new in v2.6.0

Upgrading from Milvus 2.5.x to 2.6.0 involves significant architectural changes:

  • Coordinator consolidation: Legacy separate coordinators (dataCoord, queryCoord, indexCoord) have been consolidated into a single mixCoord
  • New components: Introduction of Streaming Node for enhanced data processing
  • Component removal: indexNode removed and consolidated

This upgrade process ensures proper migration to the new architecture. For more information on architecture changes, refer to Milvus Architecture Overview.

Requirements

System requirements:

  • Helm version >= 3.14.0
  • Kubernetes version >= 1.20.0
  • Milvus standalone deployed via Helm Chart

Compatibility requirements:

  • Milvus v2.6.0-rc1 is not compatible with v2.6.0. Direct upgrades from release candidates are not supported.
  • If you are currently running v2.6.0-rc1 and need to preserve your data, please refer to this community guide for migration assistance.
  • You must upgrade to v2.5.16 or later before upgrading to v2.6.0.
Since Milvus Helm chart version 4.2.21, we introduced pulsar-v3.x chart as dependency. For backward compatibility, please upgrade your Helm to v3.14 or later version, and be sure to add the --reset-then-reuse-values option whenever you use helm upgrade.

Upgrade process

Step 1: Upgrade Helm Chart

First, upgrade your Milvus Helm chart to version 5.0.0:

helm repo add zilliztech https://zilliztech.github.io/milvus-helm
helm repo update zilliztech
The Milvus Helm Charts repo at https://milvus-io.github.io/milvus-helm/ has been archived. Use the new repo https://zilliztech.github.io/milvus-helm/ for chart versions 4.0.31 and later.

To check Helm chart version compatibility with Milvus versions:

helm search repo zilliztech/milvus --versions

This guide assumes you are installing the latest version. If you need to install a specific version, specify the --version parameter accordingly.

Step 2: Upgrade to v2.5.16

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

Upgrade your Milvus standalone to v2.5.16:

helm upgrade my-release zilliztech/milvus \
  --set image.all.tag="v2.5.16" \
  --reset-then-reuse-values \
  --version=4.2.58

Wait for the upgrade to complete:

# Verify all pods are ready
kubectl get pods

Step 3: Upgrade to v2.6.0

Once v2.5.16 is running successfully, upgrade to v2.6.0:

helm upgrade my-release zilliztech/milvus \
  --set image.all.tag="v2.6.0" \
  --reset-then-reuse-values \
  --version=5.0.0

Verify the upgrade

Confirm your standalone deployment is running the new version:

# Check pod status
kubectl get pods

For additional support, consult the Milvus documentation or community forum.

Table of contents

Try Managed Milvus for Free

Zilliz Cloud is hassle-free, powered by Milvus and 10x faster.

Get Started
Feedback

Was this page helpful?