From 3f70f08e8c20d7d52d5c13198098eae60699fa0d Mon Sep 17 00:00:00 2001 From: Sheen Capadngan Date: Tue, 17 Dec 2024 22:15:54 +0800 Subject: [PATCH] doc: added rationale for namespace installation --- docs/integrations/platforms/kubernetes.mdx | 7 ++++++- 1 file changed, 6 insertions(+), 1 deletion(-) diff --git a/docs/integrations/platforms/kubernetes.mdx b/docs/integrations/platforms/kubernetes.mdx index 77bf94e6d..ae4ee8071 100644 --- a/docs/integrations/platforms/kubernetes.mdx +++ b/docs/integrations/platforms/kubernetes.mdx @@ -43,7 +43,12 @@ The operator can be install via [Helm](https://helm.sh) or [kubectl](https://git **Namespace-scoped Installation** - The operator can be configured to watch and manage secrets in a specific namespace instead of having cluster-wide access. + The operator can be configured to watch and manage secrets in a specific namespace instead of having cluster-wide access. This is useful for: + + - **Enhanced Security**: Limit the operator's permissions to only specific namespaces instead of cluster-wide access + - **Multi-tenant Clusters**: Run separate operator instances for different teams or applications + - **Resource Isolation**: Ensure operators in different namespaces don't interfere with each other + - **Development & Testing**: Run development and production operators side by side in isolated namespaces **Note**: For multiple namespace-scoped installations, only the first installation should install CRDs. Subsequent installations should set `installCRDs: false` to avoid conflicts.