From f6e43fc336fc5cddb9206a8592ba962613470d2b Mon Sep 17 00:00:00 2001 From: davidmyriel Date: Mon, 18 Nov 2024 15:47:24 -0800 Subject: [PATCH] fix paragraph --- .../documentation/hybrid-cloud/hybrid-cloud-cluster-creation.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/qdrant-landing/content/documentation/hybrid-cloud/hybrid-cloud-cluster-creation.md b/qdrant-landing/content/documentation/hybrid-cloud/hybrid-cloud-cluster-creation.md index 1bd745dc3..b8ce004b1 100644 --- a/qdrant-landing/content/documentation/hybrid-cloud/hybrid-cloud-cluster-creation.md +++ b/qdrant-landing/content/documentation/hybrid-cloud/hybrid-cloud-cluster-creation.md @@ -173,7 +173,7 @@ With this command the secret name to enter into the UI would be `qdrant-tls` and When creating a Qdrant database cluster, Qdrant Cloud schedules Pods with specific CPU and memory requests and limits to ensure optimal performance. It’s important to use equal requests and limits for stability. Ideally, Kubernetes nodes should match the Pod size, with one database Pod per VM. -To support the operating system, Kubernetes, and system components, Qdrant Cloud reserves some resources, defaulting to 20% of available CPU and memory. This conservative default may need adjustment depending on node size, whereby smaller nodes might require more, and larger nodes less resources. +By default, Qdrant Cloud will reserve 20% of available CPU and memory. This is done to support the operating system, Kubernetes, and system components. This conservative default may need adjustment depending on node size, whereby smaller nodes might require more, and larger nodes less resources. You can modify this reservation in the “Configuration” section of the Qdrant Cluster detail page.