Skip to content

Commit

Permalink
Added note to the deploy.md (on all versions) to make people aware th…
Browse files Browse the repository at this point in the history
…at only a single metric server can handle external.metrics.k8s.io per cluster

Signed-off-by: Martijn <[email protected]>
  • Loading branch information
HemeraOne committed Dec 6, 2023
1 parent acc0b2c commit 5f2b134
Show file tree
Hide file tree
Showing 16 changed files with 81 additions and 3 deletions.
6 changes: 6 additions & 0 deletions content/docs/1.4/deploy.md
Original file line number Diff line number Diff line change
Expand Up @@ -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}
Expand Down
6 changes: 6 additions & 0 deletions content/docs/1.5/deploy.md
Original file line number Diff line number Diff line change
Expand Up @@ -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}
Expand Down
2 changes: 1 addition & 1 deletion content/docs/2.0/deploy.md
Original file line number Diff line number Diff line change
Expand Up @@ -130,4 +130,4 @@ To uninstall KEDA in MicroK8s, simply disable the addon as shown below.

```sh
microk8s disable keda
```
```
2 changes: 1 addition & 1 deletion content/docs/2.1/deploy.md
Original file line number Diff line number Diff line change
Expand Up @@ -127,4 +127,4 @@ To uninstall KEDA in MicroK8s, simply disable the addon as shown below.

```sh
microk8s disable keda
```
```
6 changes: 6 additions & 0 deletions content/docs/2.10/deploy.md
Original file line number Diff line number Diff line change
Expand Up @@ -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}
Expand Down
6 changes: 6 additions & 0 deletions content/docs/2.11/deploy.md
Original file line number Diff line number Diff line change
Expand Up @@ -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}
Expand Down
6 changes: 6 additions & 0 deletions content/docs/2.12/deploy.md
Original file line number Diff line number Diff line change
Expand Up @@ -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}
Expand Down
6 changes: 6 additions & 0 deletions content/docs/2.13/deploy.md
Original file line number Diff line number Diff line change
Expand Up @@ -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}
Expand Down
6 changes: 6 additions & 0 deletions content/docs/2.2/deploy.md
Original file line number Diff line number Diff line change
Expand Up @@ -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}
Expand Down
2 changes: 1 addition & 1 deletion content/docs/2.3/deploy.md
Original file line number Diff line number Diff line change
Expand Up @@ -121,4 +121,4 @@ To uninstall KEDA in MicroK8s, simply disable the addon as shown below.

```sh
microk8s disable keda
```
```
6 changes: 6 additions & 0 deletions content/docs/2.4/deploy.md
Original file line number Diff line number Diff line change
Expand Up @@ -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}
Expand Down
6 changes: 6 additions & 0 deletions content/docs/2.5/deploy.md
Original file line number Diff line number Diff line change
Expand Up @@ -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}
Expand Down
6 changes: 6 additions & 0 deletions content/docs/2.6/deploy.md
Original file line number Diff line number Diff line change
Expand Up @@ -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}
Expand Down
6 changes: 6 additions & 0 deletions content/docs/2.7/deploy.md
Original file line number Diff line number Diff line change
Expand Up @@ -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}
Expand Down
6 changes: 6 additions & 0 deletions content/docs/2.8/deploy.md
Original file line number Diff line number Diff line change
Expand Up @@ -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}
Expand Down
6 changes: 6 additions & 0 deletions content/docs/2.9/deploy.md
Original file line number Diff line number Diff line change
Expand Up @@ -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}
Expand Down

0 comments on commit 5f2b134

Please sign in to comment.