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

Added topic on HTTP Proxies #730

Merged
merged 3 commits into from
Mar 28, 2022
Merged

Added topic on HTTP Proxies #730

Changes from 2 commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
873d1ff
Added topic on HTTP Proxies
wltbenade Mar 25, 2022
0bbcc78
Updated wording under HTTP Proxies
wltbenade Mar 26, 2022
3212f08
Updated wording for HTTP Proxies
wltbenade Mar 28, 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
11 changes: 11 additions & 0 deletions content/docs/2.7/operate/cluster.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -65,6 +65,17 @@ $env:KEDA_HTTP_DEFAULT_TIMEOUT=1000

All applicable scalers will use this timeout. Setting a per-scaler timeout 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 the KEDA Operator deployment (HTTP_PROXY, HTTPS_PROXY, NO_PROXY, etc.) would allow the scaler to connect via the desired proxy.
wltbenade marked this conversation as resolved.
Show resolved Hide resolved

```yaml
- env:
HTTP_PROXY: http://proxy.server:port
HTTPS_PROXY: http://proxy.server:port
NO_PROXY: 10.0.0.0/8
```

## Kubernetes Client Parameters

The Kubernetes client config used within KEDA Metrics Adapter can be adjusted by passing the following command-line flags to the binary:
Expand Down