From 515d41328b4ce07dda42a9789b9823a8c5099530 Mon Sep 17 00:00:00 2001 From: Jaime Silvela Date: Thu, 28 Mar 2024 15:50:47 +0100 Subject: [PATCH] chore: clarify documentation --- README.md | 12 +++++++++++- 1 file changed, 11 insertions(+), 1 deletion(-) diff --git a/README.md b/README.md index ec3aded..6405786 100644 --- a/README.md +++ b/README.md @@ -46,7 +46,11 @@ suggested by the helm chart. It is possible to limit the operator's capabilities to solely the namespace in which it has been installed. With this restriction, the cluster-level -permissions required by the operator will be substantially reduced: +permissions required by the operator will be substantially reduced, and +the security profile of the installation is enhanced. + +You can install the operator in single-namespace mode by setting the +`config.clusterWide` flag to false, as in the following example: ```console helm upgrade --install edb-pg4k \ @@ -56,6 +60,12 @@ helm upgrade --install edb-pg4k \ edb/edb-postgres-for-kubernetes ``` +**IMPORTANT**: the single-namespace installation mode can't coexist +with the cluster-wide operator. Otherwise there would be collisions when +managing the resources in the namespace watched by the single-namespace +operator. +It is up to the user to ensure there is no collision between operators. + ### Deploying EDB Postgres for Kubernetes (PG4K) operator from EDB's private registry By default, PG4K will be deployed using [images publicly hosted on Quay.io](https://quay.io/repository/enterprisedb/cloud-native-postgresql),