From 0a0636d720f2d3ba7477a35e88817d107dc46fa2 Mon Sep 17 00:00:00 2001 From: Bastian Hofmann Date: Wed, 18 Dec 2024 11:35:06 +0100 Subject: [PATCH 1/3] Private Cloud: document different deployment scopes * only release namespace * list of namespaces * all namespaces --- .../private-cloud/private-cloud-setup.md | 28 +++++++++++++++++++ 1 file changed, 28 insertions(+) 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 29d8c26e8..d4b99adaa 100644 --- a/qdrant-landing/content/documentation/private-cloud/private-cloud-setup.md +++ b/qdrant-landing/content/documentation/private-cloud/private-cloud-setup.md @@ -88,6 +88,34 @@ For a list of available versions consult the [Private Cloud Changelog](/document Especially ensure, that the default values to reference `StorageClasses` and the corresponding `VolumeSnapshotClass` are set correctly in your environment. +### 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: + +```yaml +operator: + watch: + # If true, watches only the namespace where the Qdrant operator is deployed, otherwise watches the namespaces in watch.namespaces + onlyReleaseNamespace: false + # an empty list watches all namespaces. + namespaces: + - qdrant-private-cloud + - some-other-namespase + limitRBAC: true +``` + +Or you can configure the operator to watch all namespaces: + +```yaml +operator: + watch: + # If true, watches only the namespace where the Qdrant operator is deployed, otherwise watches the namespaces in watch.namespaces + onlyReleaseNamespace: false + # an empty list watches all namespaces. + namespaces: [] + limitRBAC: false +``` + ## Uninstallation To uninstall the Qdrant Private Cloud solution, you can use the following command: From 4f0254f8f69a8297fa79d1c8315752ce6f09d5c9 Mon Sep 17 00:00:00 2001 From: Bastian Hofmann Date: Wed, 18 Dec 2024 11:37:01 +0100 Subject: [PATCH 2/3] 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: From bb7a576c95aa0cfd7b5cc7cfa8a91454d359d9a1 Mon Sep 17 00:00:00 2001 From: Bastian Hofmann Date: Wed, 18 Dec 2024 16:50:16 +0100 Subject: [PATCH 3/3] Fix typo --- .../content/documentation/private-cloud/private-cloud-setup.md | 2 +- 1 file changed, 1 insertion(+), 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 8a52e9228..b191c76fc 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,7 @@ 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. This default is chosen to limit the operator to the least amount of permissions necessary within a Kubernetes clusters. +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 cluster. 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: