From 4f0254f8f69a8297fa79d1c8315752ce6f09d5c9 Mon Sep 17 00:00:00 2001 From: Bastian Hofmann Date: Wed, 18 Dec 2024 11:37:01 +0100 Subject: [PATCH] Add reason --- .../documentation/private-cloud/private-cloud-setup.md | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/qdrant-landing/content/documentation/private-cloud/private-cloud-setup.md b/qdrant-landing/content/documentation/private-cloud/private-cloud-setup.md index d4b99adaa..8a52e9228 100644 --- a/qdrant-landing/content/documentation/private-cloud/private-cloud-setup.md +++ b/qdrant-landing/content/documentation/private-cloud/private-cloud-setup.md @@ -90,7 +90,9 @@ Especially ensure, that the default values to reference `StorageClasses` and the ### Scope of the operator -By default, the Qdrant Operator will only manage Qdrant clusters in the same Kubernetes namespace, where it is already deployed. The RoleBindings are also limited to this specific namespace. If you want to manage Qdrant clusters in multiple namespaces with the same operator, you can either configure a list of namespaces that the operator should watch: +By default, the Qdrant Operator will only manage Qdrant clusters in the same Kubernetes namespace, where it is already deployed. The RoleBindings are also limited to this specific namespace. This default is chosen to limit the operator to the least amount of permissions necessary within a Kubernetes clusters. + +If you want to manage Qdrant clusters in multiple namespaces with the same operator, you can either configure a list of namespaces that the operator should watch: ```yaml operator: