From 1d464ad985f68d086d3e548ccb13cdef93d61c1f Mon Sep 17 00:00:00 2001 From: timvisee Date: Fri, 9 May 2025 11:43:57 +0200 Subject: [PATCH] In the upgrade instructions, align to latest Qdrant patch versions --- .../documentation/private-cloud/qdrant-cluster-management.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/qdrant-landing/content/documentation/private-cloud/qdrant-cluster-management.md b/qdrant-landing/content/documentation/private-cloud/qdrant-cluster-management.md index f367ff7ec..f1106f7e6 100644 --- a/qdrant-landing/content/documentation/private-cloud/qdrant-cluster-management.md +++ b/qdrant-landing/content/documentation/private-cloud/qdrant-cluster-management.md @@ -39,7 +39,7 @@ To scale a cluster, update the CPU, memory and storage resources in the QdrantCl To upgrade the Qdrant version of a database cluster, update the `version` field in the QdrantCluster spec. The Qdrant operator will automatically upgrade the cluster to the new version. The upgrade process is highly available on a multi-node cluster with replicated collections. -Note, that you should not skip minor versions when upgrading. For example, if you are running version `v1.11.3`, you can upgrade to `v1.11.4` or `v1.12.2`, but not directly to `v1.13.0`. +Note, that you should not skip minor versions when upgrading. For example, if you are running version `v1.11.3`, you can upgrade to `v1.11.5` or `v1.12.6`, but not directly to `v1.13.0`. ## Exposing a Cluster