Merge upstream PR redis#3343 (DOC-6630) into feature/docker-support

RDI: note about one install per k8s cluster.

Upstream merge commit: e2632e0
Commits: 6828b0c, 2d40703

Author: EliShteinman

content/integrate/redis-data-integration/faq.md

@@ -55,6 +55,14 @@ The configuration for the GCS is available only for [Helm based installations]({
 
 **Important:** You should only use this configuration when both sites use the same source configuration.
 
+## Can I run multiple RDI installations in the same Kubernetes cluster?
+
+No. Only one RDI installation is supported per Kubernetes cluster, even if
+you install into different namespaces. If you need more than one RDI
+deployment, use separate Kubernetes clusters. See
+[Install on Kubernetes]({{< relref "/integrate/redis-data-integration/installation/install-k8s" >}})
+for installation details.
+
 ## Can RDI automatically track changes to the source database schema?
 
 If you don't configure RDI to capture a specific set of tables in the schema then it will

content/integrate/redis-data-integration/installation/install-k8s.md

@@ -173,7 +173,13 @@ To pull images from a private image registry, you must provide the image pull se
     {{< note >}}The above command will install RDI in a namespace called
     `rdi`. If you want to use a different namespace, pass the option
     `-n <custom-namespace>` to the `helm install` command instead.
-    {{< /note >}} 
+    {{< /note >}}
+    &nbsp;
+    {{< warning >}}Only one RDI installation is supported per Kubernetes
+    cluster. Installing RDI into multiple namespaces in the same cluster is
+    not supported and will fail. If you need more than one RDI deployment,
+    use separate Kubernetes clusters.
+    {{< /warning >}} 
 
 ### The `values.yaml` file