Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

support disable keep alive http connection #982

Merged
merged 3 commits into from
Dec 9, 2022
Merged

support disable keep alive http connection #982

Changes from 1 commit
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
728cfe9
Support disable keep http connection alive
penghuazhou Nov 26, 2022
63b81d5
point users here to env KEDA_HTTP_DISABLE_KEEP_ALIVE in Kubernetes De…
penghuazhou Nov 30, 2022
2146ebf
change variables to variable
penghuazhou Nov 30, 2022
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
17 changes: 17 additions & 0 deletions content/docs/2.9/operate/cluster.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -75,6 +75,23 @@ $env:KEDA_HTTP_DEFAULT_TIMEOUT=1000

All applicable scalers will use this timeout. Setting a per-scaler timeout is currently unsupported.

## HTTP connection disable keep alive

Keep alive behaviour is enabled by default for every HTTP connection, this could stack a huge amount of connections (one per scaler) in some scenarios.

You can override this default setting `KEDA_HTTP_DISABLE_KEEP_ALIVE` environment variable to true. For example, on Linux/Mac/Windows WSL2 operating systems, you'd use this command to set to true:

```shell
export KEDA_HTTP_DISABLE_KEEP_ALIVE=true
```

And on Windows Powershell, you'd use this command:

```shell
$env:KEDA_HTTP_DISABLE_KEEP_ALIVE=true
```
All applicable scalers will use this keep alive behaviour. Setting a per-scaler keep alive behaviour is currently unsupported.

## HTTP Proxies

Some scalers issue HTTP requests to external servers (i.e. cloud services). As certain companies require external servers to be accessed by proxy servers, adding the relevant environment variables to both the KEDA Operator, and KEDA Metrics Server deployments (HTTP_PROXY, HTTPS_PROXY, NO_PROXY, etc.) would allow the scaler to connect via the desired proxy.
Expand Down