diff --git a/content/docs/1.4/deploy.md b/content/docs/1.4/deploy.md
index ed179f91b..6e594ce09 100644
--- a/content/docs/1.4/deploy.md
+++ b/content/docs/1.4/deploy.md
@@ -8,6 +8,12 @@ We provide a few approaches to deploy KEDA runtime in your Kubernetes clusters:
 - [Operator Hub](#operatorhub)
 - [YAML declarations](#yaml)
 
+> 💡 **NOTE:** Kubernetes currently only supports one metric server serving external.metrics.k8s.io metrics per cluster. This is because only one API Service can be registered to handle external metrics.
+>
+> After installing KEDA, any other metric servers that you have installed will no longer be able to serve external metrics.
+>
+> There is an [open proposal](https://github.com/kubernetes-sigs/custom-metrics-apiserver/issues/70) to allow multiple metric servers in the same cluster, but it's not implemented yet.
+
 Don't see what you need? Feel free to [create an issue](https://github.com/kedacore/keda/issues/new) on our GitHub repo.
 
 ## Deploying with Helm {#helm}
diff --git a/content/docs/1.5/deploy.md b/content/docs/1.5/deploy.md
index 657224507..690a9ba8a 100644
--- a/content/docs/1.5/deploy.md
+++ b/content/docs/1.5/deploy.md
@@ -8,6 +8,12 @@ We provide a few approaches to deploy KEDA runtime in your Kubernetes clusters:
 - [Operator Hub](#operatorhub)
 - [YAML declarations](#yaml)
 
+> 💡 **NOTE:** Kubernetes currently only supports one metric server serving external.metrics.k8s.io metrics per cluster. This is because only one API Service can be registered to handle external metrics.
+>
+> After installing KEDA, any other metric servers that you have installed will no longer be able to serve external metrics.
+>
+> There is an [open proposal](https://github.com/kubernetes-sigs/custom-metrics-apiserver/issues/70) to allow multiple metric servers in the same cluster, but it's not implemented yet.
+
 Don't see what you need? Feel free to [create an issue](https://github.com/kedacore/keda/issues/new) on our GitHub repo.
 
 ## Deploying with Helm {#helm}
diff --git a/content/docs/2.0/deploy.md b/content/docs/2.0/deploy.md
index 56433d832..251957589 100644
--- a/content/docs/2.0/deploy.md
+++ b/content/docs/2.0/deploy.md
@@ -130,4 +130,4 @@ To uninstall KEDA in MicroK8s, simply disable the addon as shown below.
 
 ```sh
 microk8s disable keda
-```
\ No newline at end of file
+```
diff --git a/content/docs/2.1/deploy.md b/content/docs/2.1/deploy.md
index 6fe5ed9ca..1d6eafa78 100644
--- a/content/docs/2.1/deploy.md
+++ b/content/docs/2.1/deploy.md
@@ -127,4 +127,4 @@ To uninstall KEDA in MicroK8s, simply disable the addon as shown below.
 
 ```sh
 microk8s disable keda
-```
\ No newline at end of file
+```
diff --git a/content/docs/2.10/deploy.md b/content/docs/2.10/deploy.md
index 7dddcba8e..17885d9ce 100644
--- a/content/docs/2.10/deploy.md
+++ b/content/docs/2.10/deploy.md
@@ -10,6 +10,12 @@ We provide a few approaches to deploy KEDA runtime in your Kubernetes clusters:
 
 > 💡 **NOTE:** KEDA requires Kubernetes cluster version 1.24 and higher
 
+> 💡 **NOTE:** Kubernetes currently only supports one metric server serving external.metrics.k8s.io metrics per cluster. This is because only one API Service can be registered to handle external metrics.
+>
+> After installing KEDA, any other metric servers that you have installed will no longer be able to serve external metrics.
+>
+> There is an [open proposal](https://github.com/kubernetes-sigs/custom-metrics-apiserver/issues/70) to allow multiple metric servers in the same cluster, but it's not implemented yet.
+
 Don't see what you need? Feel free to [create an issue](https://github.com/kedacore/keda/issues/new) on our GitHub repo.
 
 ## Deploying with Helm {#helm}
diff --git a/content/docs/2.11/deploy.md b/content/docs/2.11/deploy.md
index 9d3bb6abf..ebb7db4e9 100644
--- a/content/docs/2.11/deploy.md
+++ b/content/docs/2.11/deploy.md
@@ -10,6 +10,12 @@ We provide a few approaches to deploy KEDA runtime in your Kubernetes clusters:
 
 > 💡 **NOTE:** KEDA requires Kubernetes cluster version 1.24 and higher
 
+> 💡 **NOTE:** Kubernetes currently only supports one metric server serving external.metrics.k8s.io metrics per cluster. This is because only one API Service can be registered to handle external metrics.
+>
+> After installing KEDA, any other metric servers that you have installed will no longer be able to serve external metrics.
+>
+> There is an [open proposal](https://github.com/kubernetes-sigs/custom-metrics-apiserver/issues/70) to allow multiple metric servers in the same cluster, but it's not implemented yet.
+
 Don't see what you need? Feel free to [create an issue](https://github.com/kedacore/keda/issues/new) on our GitHub repo.
 
 ## Deploying with Helm {#helm}
diff --git a/content/docs/2.12/deploy.md b/content/docs/2.12/deploy.md
index 3ed2cdb93..2e5a79a3a 100644
--- a/content/docs/2.12/deploy.md
+++ b/content/docs/2.12/deploy.md
@@ -10,6 +10,12 @@ We provide a few approaches to deploy KEDA runtime in your Kubernetes clusters:
 
 > 💡 **NOTE:** KEDA requires Kubernetes cluster version 1.24 and higher
 
+> 💡 **NOTE:** Kubernetes currently only supports one metric server serving external.metrics.k8s.io metrics per cluster. This is because only one API Service can be registered to handle external metrics.
+>
+> After installing KEDA, any other metric servers that you have installed will no longer be able to serve external metrics.
+>
+> There is an [open proposal](https://github.com/kubernetes-sigs/custom-metrics-apiserver/issues/70) to allow multiple metric servers in the same cluster, but it's not implemented yet.
+
 Don't see what you need? Feel free to [create an issue](https://github.com/kedacore/keda/issues/new) on our GitHub repo.
 
 ## Deploying with Helm {#helm}
diff --git a/content/docs/2.13/deploy.md b/content/docs/2.13/deploy.md
index e3f60aaa5..ef20a4186 100644
--- a/content/docs/2.13/deploy.md
+++ b/content/docs/2.13/deploy.md
@@ -10,6 +10,12 @@ We provide a few approaches to deploy KEDA runtime in your Kubernetes clusters:
 
 > 💡 **NOTE:** KEDA requires Kubernetes cluster version 1.24 and higher
 
+> 💡 **NOTE:** Kubernetes currently only supports one metric server serving external.metrics.k8s.io metrics per cluster. This is because only one API Service can be registered to handle external metrics.
+>
+> After installing KEDA, any other metric servers that you have installed will no longer be able to serve external metrics.
+>
+> There is an [open proposal](https://github.com/kubernetes-sigs/custom-metrics-apiserver/issues/70) to allow multiple metric servers in the same cluster, but it's not implemented yet.
+
 Don't see what you need? Feel free to [create an issue](https://github.com/kedacore/keda/issues/new) on our GitHub repo.
 
 ## Deploying with Helm {#helm}
diff --git a/content/docs/2.2/deploy.md b/content/docs/2.2/deploy.md
index 8fb51b420..30ac33f1b 100644
--- a/content/docs/2.2/deploy.md
+++ b/content/docs/2.2/deploy.md
@@ -10,6 +10,12 @@ We provide a few approaches to deploy KEDA runtime in your Kubernetes clusters:
 
 > 💡 **NOTE:** KEDA requires Kubernetes cluster version 1.16 and higher
 
+> 💡 **NOTE:** Kubernetes currently only supports one metric server serving external.metrics.k8s.io metrics per cluster. This is because only one API Service can be registered to handle external metrics.
+>
+> After installing KEDA, any other metric servers that you have installed will no longer be able to serve external metrics.
+>
+> There is an [open proposal](https://github.com/kubernetes-sigs/custom-metrics-apiserver/issues/70) to allow multiple metric servers in the same cluster, but it's not implemented yet.
+
 Don't see what you need? Feel free to [create an issue](https://github.com/kedacore/keda/issues/new) on our GitHub repo.
 
 ## Deploying with Helm {#helm}
diff --git a/content/docs/2.3/deploy.md b/content/docs/2.3/deploy.md
index 9a535da31..005204ab0 100644
--- a/content/docs/2.3/deploy.md
+++ b/content/docs/2.3/deploy.md
@@ -121,4 +121,4 @@ To uninstall KEDA in MicroK8s, simply disable the addon as shown below.
 
 ```sh
 microk8s disable keda
-```
\ No newline at end of file
+```
diff --git a/content/docs/2.4/deploy.md b/content/docs/2.4/deploy.md
index 8f0c93122..cc5e6c0e0 100644
--- a/content/docs/2.4/deploy.md
+++ b/content/docs/2.4/deploy.md
@@ -10,6 +10,12 @@ We provide a few approaches to deploy KEDA runtime in your Kubernetes clusters:
 
 > 💡 **NOTE:** KEDA requires Kubernetes cluster version 1.16 and higher
 
+> 💡 **NOTE:** Kubernetes currently only supports one metric server serving external.metrics.k8s.io metrics per cluster. This is because only one API Service can be registered to handle external metrics.
+>
+> After installing KEDA, any other metric servers that you have installed will no longer be able to serve external metrics.
+>
+> There is an [open proposal](https://github.com/kubernetes-sigs/custom-metrics-apiserver/issues/70) to allow multiple metric servers in the same cluster, but it's not implemented yet.
+
 Don't see what you need? Feel free to [create an issue](https://github.com/kedacore/keda/issues/new) on our GitHub repo.
 
 ## Deploying with Helm {#helm}
diff --git a/content/docs/2.5/deploy.md b/content/docs/2.5/deploy.md
index 7d4cb35db..f2abc737f 100644
--- a/content/docs/2.5/deploy.md
+++ b/content/docs/2.5/deploy.md
@@ -10,6 +10,12 @@ We provide a few approaches to deploy KEDA runtime in your Kubernetes clusters:
 
 > 💡 **NOTE:** KEDA requires Kubernetes cluster version 1.16 and higher
 
+> 💡 **NOTE:** Kubernetes currently only supports one metric server serving external.metrics.k8s.io metrics per cluster. This is because only one API Service can be registered to handle external metrics.
+>
+> After installing KEDA, any other metric servers that you have installed will no longer be able to serve external metrics.
+>
+> There is an [open proposal](https://github.com/kubernetes-sigs/custom-metrics-apiserver/issues/70) to allow multiple metric servers in the same cluster, but it's not implemented yet.
+
 Don't see what you need? Feel free to [create an issue](https://github.com/kedacore/keda/issues/new) on our GitHub repo.
 
 ## Deploying with Helm {#helm}
diff --git a/content/docs/2.6/deploy.md b/content/docs/2.6/deploy.md
index e7ea1e6be..548e81250 100644
--- a/content/docs/2.6/deploy.md
+++ b/content/docs/2.6/deploy.md
@@ -10,6 +10,12 @@ We provide a few approaches to deploy KEDA runtime in your Kubernetes clusters:
 
 > 💡 **NOTE:** KEDA requires Kubernetes cluster version 1.16 and higher
 
+> 💡 **NOTE:** Kubernetes currently only supports one metric server serving external.metrics.k8s.io metrics per cluster. This is because only one API Service can be registered to handle external metrics.
+>
+> After installing KEDA, any other metric servers that you have installed will no longer be able to serve external metrics.
+>
+> There is an [open proposal](https://github.com/kubernetes-sigs/custom-metrics-apiserver/issues/70) to allow multiple metric servers in the same cluster, but it's not implemented yet.
+
 Don't see what you need? Feel free to [create an issue](https://github.com/kedacore/keda/issues/new) on our GitHub repo.
 
 ## Deploying with Helm {#helm}
diff --git a/content/docs/2.7/deploy.md b/content/docs/2.7/deploy.md
index 19bc267f4..3da9f7d13 100644
--- a/content/docs/2.7/deploy.md
+++ b/content/docs/2.7/deploy.md
@@ -10,6 +10,12 @@ We provide a few approaches to deploy KEDA runtime in your Kubernetes clusters:
 
 > 💡 **NOTE:** KEDA requires Kubernetes cluster version 1.16 and higher
 
+> 💡 **NOTE:** Kubernetes currently only supports one metric server serving external.metrics.k8s.io metrics per cluster. This is because only one API Service can be registered to handle external metrics.
+>
+> After installing KEDA, any other metric servers that you have installed will no longer be able to serve external metrics.
+>
+> There is an [open proposal](https://github.com/kubernetes-sigs/custom-metrics-apiserver/issues/70) to allow multiple metric servers in the same cluster, but it's not implemented yet.
+
 Don't see what you need? Feel free to [create an issue](https://github.com/kedacore/keda/issues/new) on our GitHub repo.
 
 ## Deploying with Helm {#helm}
diff --git a/content/docs/2.8/deploy.md b/content/docs/2.8/deploy.md
index 197df69fa..4812a225e 100644
--- a/content/docs/2.8/deploy.md
+++ b/content/docs/2.8/deploy.md
@@ -10,6 +10,12 @@ We provide a few approaches to deploy KEDA runtime in your Kubernetes clusters:
 
 > 💡 **NOTE:** KEDA requires Kubernetes cluster version 1.16 and higher
 
+> 💡 **NOTE:** Kubernetes currently only supports one metric server serving external.metrics.k8s.io metrics per cluster. This is because only one API Service can be registered to handle external metrics.
+>
+> After installing KEDA, any other metric servers that you have installed will no longer be able to serve external metrics.
+>
+> There is an [open proposal](https://github.com/kubernetes-sigs/custom-metrics-apiserver/issues/70) to allow multiple metric servers in the same cluster, but it's not implemented yet.
+
 Don't see what you need? Feel free to [create an issue](https://github.com/kedacore/keda/issues/new) on our GitHub repo.
 
 ## Deploying with Helm {#helm}
diff --git a/content/docs/2.9/deploy.md b/content/docs/2.9/deploy.md
index 2f231530f..1f9aed609 100644
--- a/content/docs/2.9/deploy.md
+++ b/content/docs/2.9/deploy.md
@@ -10,6 +10,12 @@ We provide a few approaches to deploy KEDA runtime in your Kubernetes clusters:
 
 > 💡 **NOTE:** KEDA requires Kubernetes cluster version 1.23 and higher
 
+> 💡 **NOTE:** Kubernetes currently only supports one metric server serving external.metrics.k8s.io metrics per cluster. This is because only one API Service can be registered to handle external metrics.
+>
+> After installing KEDA, any other metric servers that you have installed will no longer be able to serve external metrics.
+>
+> There is an [open proposal](https://github.com/kubernetes-sigs/custom-metrics-apiserver/issues/70) to allow multiple metric servers in the same cluster, but it's not implemented yet.
+
 Don't see what you need? Feel free to [create an issue](https://github.com/kedacore/keda/issues/new) on our GitHub repo.
 
 ## Deploying with Helm {#helm}