Merge pull request #3263 from liyun95/preview

update 2.6.0 upgrade guide

Author: liyun95

site/en/adminGuide/upgrade_milvus_cluster-helm.md

@@ -18,15 +18,7 @@ This guide describes how to upgrade your Milvus cluster from v2.5.x to v{{var.mi
 
 ### What's new in v{{var.milvus_release_version}}
 
-Upgrading from Milvus 2.5.x to {{var.milvus_release_version}} involves significant architectural changes:
-
-- **Coordinator consolidation**: Legacy separate coordinators (`dataCoordinator`, `queryCoordinator`, `indexCoordinator`) have been consolidated into a single `mixCoordinator`
-- **New components**: Introduction of Streaming Node and other new components  
-- **Component removal**: Certain legacy components including `indexNode` have been removed
-
-<div class="alert note">
-This upgrade is <strong>irreversible</strong>. You cannot roll back to a previous version once the upgrade is completed. For details on architectural changes, refer to <a href="architecture_overview.md">Milvus Architecture Overview</a>.
-</div>
+As of Milvus 2.6.0, the legacy separate coordinators (`dataCoord`, `queryCoord`, `indexCoord`) have been consolidated into a single `mixCoord`. This upgrade process ensures proper migration to the new architecture. For more information on architecture changes, refer to [Milvus Architecture Overview](architecture_overview.md).
 
 ### Requirements
 
@@ -121,9 +113,6 @@ Confirm your cluster is running the new version:
 ```bash
 # Check pod status
 kubectl get pods
-
-# Verify Helm release
-helm list
 ```
 
 For additional support, consult the [Milvus documentation](https://milvus.io/docs) or [community forum](https://github.com/milvus-io/milvus/discussions).

site/en/adminGuide/upgrade_milvus_cluster-operator.md

@@ -92,9 +92,6 @@ kubectl patch -f milvusupgrade.yaml --patch-file milvusupgrade.yaml --type merge
 Wait for completion:
 
 ```bash
-# Monitor the upgrade progress
-kubectl get pods -w
-
 # Verify all pods are ready
 kubectl get pods
 ```

site/en/adminGuide/upgrade_milvus_standalone-helm.md

@@ -19,16 +19,7 @@ This guide describes how to upgrade your Milvus standalone deployment from v2.5.
 
 ### What's new in v{{var.milvus_release_version}}
 
-Upgrading from Milvus 2.5.x to {{var.milvus_release_version}} involves significant architectural changes:
-
-- **New components**: Introduction of Streaming Node and other new components
-- **Component optimizations**: Enhanced performance and streamlined architecture
-
-This upgrade process ensures proper migration to the new architecture. For more information on architecture changes, refer to <a href="architecture_overview.md">Milvus Architecture Overview</a>.
-
-<div class="alert note">
-This upgrade is <strong>irreversible</strong>. You cannot roll back to a previous version once the upgrade is completed.
-</div>
+As of Milvus 2.6.0, the legacy separate coordinators (`dataCoord`, `queryCoord`, `indexCoord`) have been consolidated into a single `mixCoord`. This upgrade process ensures proper migration to the new architecture. For more information on architecture changes, refer to [Milvus Architecture Overview](architecture_overview.md).
 
 ### Requirements
 

site/en/adminGuide/upgrade_milvus_standalone-operator.md

@@ -18,16 +18,7 @@ This guide describes how to upgrade your Milvus standalone deployment from v2.5.
 
 ### What's new in v{{var.milvus_release_version}}
 
-Upgrading from Milvus 2.5.x to {{var.milvus_release_version}} involves significant architectural changes:
-
-- **New components**: Introduction of Streaming Node and other new components
-- **Component optimizations**: Enhanced performance and streamlined architecture for standalone deployments
-
-This upgrade process ensures proper migration to the new architecture. For more information on architecture changes, refer to <a href="architecture_overview.md">Milvus Architecture Overview</a>.
-
-<div class="alert note">
-This upgrade is <strong>irreversible</strong>. You cannot roll back to a previous version once the upgrade is completed.
-</div>
+As of Milvus 2.6.0, the legacy separate coordinators (`dataCoord`, `queryCoord`, `indexCoord`) have been consolidated into a single `mixCoord`. This upgrade process ensures proper migration to the new architecture. For more information on architecture changes, refer to [Milvus Architecture Overview](architecture_overview.md).
 
 ### Requirements
 

site/en/getstarted/run-milvus-k8s/install_cluster-helm.md

@@ -69,7 +69,6 @@ Once you have installed the Helm chart, you can start Milvus on Kubernetes. This
 <strong>Need standalone deployment instead?</strong>
 
 If you prefer to deploy Milvus in standalone mode (single node) for development or testing, use this command:
-
 ```bash
 helm install my-release zilliztech/milvus \
   --set image.all.tag=v{{var.milvus_release_version}} \
@@ -111,10 +110,6 @@ For complete architecture details, refer to the [Architecture Overview](architec
 
 </div>
 
-**Command parameters:**
-- `my-release`: Your deployment name (use letters, numbers, and dashes only)
-- `zilliztech/milvus`: The Helm chart repository
-
 **Next steps:**
 The command above deploys Milvus with default configurations. For production use:
 - Use the [Milvus Sizing Tool](https://milvus.io/tools/sizing) to optimize settings based on your data size
@@ -171,10 +166,6 @@ my-release-pulsar-zookeeper-0                    1/1    Running   0        3m23s
 my-release-pulsar-zookeeper-metadata-98zbr       0/1   Completed  0        3m24s
 ```
 
-**Key components to verify:**
-- **Milvus components**: `mixcoord`, `datanode`, `querynode`, `proxy`, `streaming-node`
-- **Dependencies**: `etcd` (metadata), `minio` (object storage), `pulsar` (message queue)
-
 You can also access the **Milvus WebUI** at `http://127.0.0.1:9091/webui/` once port forwarding is set up (see next step). For details, refer to [Milvus WebUI](milvus-webui.md).
 
 ### 3. Connect to Milvus