From 873d1ffde5c7542a9bb5218b27ab0ddc6a9cb174 Mon Sep 17 00:00:00 2001 From: wltbenade <66667751+wltbenade@users.noreply.github.com> Date: Fri, 25 Mar 2022 13:48:22 +0200 Subject: [PATCH 1/3] Added topic on HTTP Proxies --- content/docs/2.7/operate/cluster.md | 11 +++++++++++ 1 file changed, 11 insertions(+) diff --git a/content/docs/2.7/operate/cluster.md b/content/docs/2.7/operate/cluster.md index 20d78baf3..cdf10c397 100644 --- a/content/docs/2.7/operate/cluster.md +++ b/content/docs/2.7/operate/cluster.md @@ -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 your deployment (HTTP_PROXY, HTTPS_PROXY, NO_PROXY, etc.) would allow the scaler to connect via the desired proxy. + +```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: From 0bbcc7856ec548855333d5c8fda067bec65f9838 Mon Sep 17 00:00:00 2001 From: wltbenade <66667751+wltbenade@users.noreply.github.com> Date: Sat, 26 Mar 2022 12:14:55 +0200 Subject: [PATCH 2/3] Updated wording under HTTP Proxies As per @zroubalik's suggestion. --- content/docs/2.7/operate/cluster.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/content/docs/2.7/operate/cluster.md b/content/docs/2.7/operate/cluster.md index cdf10c397..e18cbf9a8 100644 --- a/content/docs/2.7/operate/cluster.md +++ b/content/docs/2.7/operate/cluster.md @@ -67,7 +67,7 @@ All applicable scalers will use this timeout. Setting a per-scaler timeout is cu ## 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 your deployment (HTTP_PROXY, HTTPS_PROXY, NO_PROXY, etc.) would allow the scaler to connect via the desired proxy. +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. ```yaml - env: From 3212f0823f382613fa8436b9ad5b7c3747a6eabc Mon Sep 17 00:00:00 2001 From: wltbenade <66667751+wltbenade@users.noreply.github.com> Date: Mon, 28 Mar 2022 09:35:37 +0200 Subject: [PATCH 3/3] Updated wording for HTTP Proxies As per @zroubalik's suggestion. --- content/docs/2.7/operate/cluster.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/content/docs/2.7/operate/cluster.md b/content/docs/2.7/operate/cluster.md index e18cbf9a8..d6fab8ff0 100644 --- a/content/docs/2.7/operate/cluster.md +++ b/content/docs/2.7/operate/cluster.md @@ -67,7 +67,7 @@ All applicable scalers will use this timeout. Setting a per-scaler timeout is cu ## 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. +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. ```yaml - env: