Skip to content

Commit

Permalink
Document running multiple operator instances (kedacore#615)
Browse files Browse the repository at this point in the history 
* Document running multiple operator instances thanks to @mtparet

Signed-off-by: Tom Kerkhove <[email protected]>

* Incorporate @arschles his feedback

Signed-off-by: Tom Kerkhove <[email protected]>

* Incorporate @arschles his feedback

Signed-off-by: Tom Kerkhove <[email protected]>

* Delete settings.json

Signed-off-by: Tom Kerkhove <[email protected]>
  • Loading branch information
@tomkerkhove
tomkerkhove authored Jan 6, 2022
1 parent 02244a9 commit 3b6dce3
Show file tree
Hide file tree
Showing 6 changed files with 8 additions and 8 deletions.
4 changes: 2 additions & 2 deletions content/docs/2.1/operate/cluster.md
View file
Original file line number Diff line number Diff line change
Expand Up @@ -36,12 +36,12 @@ Here is an overview of all KEDA deployments and the supported replicas:

| Deployment | Support Replicas | Reasoning |
|----------------|-------------------------|-------------------------------|
| Operator | 1 | |
| Operator | 2 | While you can run more replicas of our operator, only one operator instance will be active. The rest will be standing by, which may reduce downtime during a failure. Multiple replicas will not improve the performance of KEDA, it might only reduce downtime during a failover.<br /><br />This is only supported as of KEDA v2.6 if you are using our Helm chart.|
| Metrics Server | 1 | Limitation in [k8s custom metrics server](https://github.com/kubernetes-sigs/custom-metrics-apiserver/issues/70) |

## HTTP Timeouts

Some scalers issue HTTP requests to external servers (i.e. cloud services). Each applicable scaler uses its own dedicated HTTP client with its own connection pool, and by default each client is set to time out any HTTP request after 3 seconds.
Some scalers issue HTTP requests to external servers (i.e. cloud services). Each applicable scaler uses its own dedicated HTTP client with its own connection pool, and by default each client is set to time out any HTTP request after 3 seconds.

You can override this default by setting the `KEDA_HTTP_DEFAULT_TIMEOUT` environment variable to your desired timeout in milliseconds. For example, on Linux/Mac/Windows WSL2 operating systems, you'd use this command to set to 1 second:

Expand Down
4 changes: 2 additions & 2 deletions content/docs/2.2/operate/cluster.md
View file
Original file line number Diff line number Diff line change
Expand Up @@ -39,11 +39,11 @@ Here is an overview of all KEDA deployments and the supported replicas:
| Deployment | Support Replicas | Reasoning |
| -------------- | ---------------- | ---------------------------------------------------------------------------------------------------------------- |
| Metrics Server | 1 | Limitation in [k8s custom metrics server](https://github.com/kubernetes-sigs/custom-metrics-apiserver/issues/70) |
| Operator | 1 | |
| Operator | 2 | While you can run more replicas of our operator, only one operator instance will be active. The rest will be standing by, which may reduce downtime during a failure. Multiple replicas will not improve the performance of KEDA, it might only reduce downtime during a failover.<br /><br />This is only supported as of KEDA v2.6 if you are using our Helm chart.|

## HTTP Timeouts

Some scalers issue HTTP requests to external servers (i.e. cloud services). Each applicable scaler uses its own dedicated HTTP client with its own connection pool, and by default each client is set to time out any HTTP request after 3 seconds.
Some scalers issue HTTP requests to external servers (i.e. cloud services). Each applicable scaler uses its own dedicated HTTP client with its own connection pool, and by default each client is set to time out any HTTP request after 3 seconds.

You can override this default by setting the `KEDA_HTTP_DEFAULT_TIMEOUT` environment variable to your desired timeout in milliseconds. For example, on Linux/Mac/Windows WSL2 operating systems, you'd use this command to set to 1 second:

Expand Down
2 changes: 1 addition & 1 deletion content/docs/2.3/operate/cluster.md
View file
Original file line number Diff line number Diff line change
Expand Up @@ -39,7 +39,7 @@ Here is an overview of all KEDA deployments and the supported replicas:
| Deployment | Support Replicas | Reasoning |
| -------------- | ---------------- | ---------------------------------------------------------------------------------------------------------------- |
| Metrics Server | 1 | Limitation in [k8s custom metrics server](https://github.com/kubernetes-sigs/custom-metrics-apiserver/issues/70) |
| Operator | 1 | |
| Operator | 2 | While you can run more replicas of our operator, only one operator instance will be active. The rest will be standing by, which may reduce downtime during a failure. Multiple replicas will not improve the performance of KEDA, it might only reduce downtime during a failover.<br /><br />This is only supported as of KEDA v2.6 if you are using our Helm chart.|

## HTTP Timeouts

Expand Down
2 changes: 1 addition & 1 deletion content/docs/2.4/operate/cluster.md
View file
Original file line number Diff line number Diff line change
Expand Up @@ -39,7 +39,7 @@ Here is an overview of all KEDA deployments and the supported replicas:
| Deployment | Support Replicas | Reasoning |
| -------------- | ---------------- | ---------------------------------------------------------------------------------------------------------------- |
| Metrics Server | 1 | Limitation in [k8s custom metrics server](https://github.com/kubernetes-sigs/custom-metrics-apiserver/issues/70) |
| Operator | 1 | |
| Operator | 2 | While you can run more replicas of our operator, only one operator instance will be active. The rest will be standing by, which may reduce downtime during a failure. Multiple replicas will not improve the performance of KEDA, it might only reduce downtime during a failover.<br /><br />This is only supported as of KEDA v2.6 if you are using our Helm chart.|

## HTTP Timeouts

Expand Down
2 changes: 1 addition & 1 deletion content/docs/2.5/operate/cluster.md
View file
Original file line number Diff line number Diff line change
Expand Up @@ -39,7 +39,7 @@ Here is an overview of all KEDA deployments and the supported replicas:
| Deployment | Support Replicas | Reasoning |
| -------------- | ---------------- | ---------------------------------------------------------------------------------------------------------------- |
| Metrics Server | 1 | Limitation in [k8s custom metrics server](https://github.com/kubernetes-sigs/custom-metrics-apiserver/issues/70) |
| Operator | 1 | |
| Operator | 2 | While you can run more replicas of our operator, only one operator instance will be active. The rest will be standing by, which may reduce downtime during a failure. Multiple replicas will not improve the performance of KEDA, it might only reduce downtime during a failover.|

## HTTP Timeouts

Expand Down
2 changes: 1 addition & 1 deletion content/docs/2.6/operate/cluster.md
View file
Original file line number Diff line number Diff line change
Expand Up @@ -39,7 +39,7 @@ Here is an overview of all KEDA deployments and the supported replicas:
| Deployment | Support Replicas | Reasoning |
| -------------- | ---------------- | ---------------------------------------------------------------------------------------------------------------- |
| Metrics Server | 1 | Limitation in [k8s custom metrics server](https://github.com/kubernetes-sigs/custom-metrics-apiserver/issues/70) |
| Operator | 1 | |
| Operator | 2 | While you can run more replicas of our operator, only one operator instance will be active. The rest will be standing by, which may reduce downtime during a failure. Multiple replicas will not improve the performance of KEDA, it could only reduce a downtime during a failover.|

## HTTP Timeouts

Expand Down

0 comments on commit 3b6dce3

Please sign in to comment.