You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
feat(proxy) : Config supports proxy-url field in .kube/config cluster configuration
Set Config's `httpProxy` / `httpsProxy` fields if current context's
cluster configuration has `proxy-url` set
Signed-off-by: Rohan Kumar <[email protected]>
|`kubernetes.backwardsCompatibilityInterceptor.disable` / `KUBERNETES_BACKWARDSCOMPATIBILITYINTERCEPTOR_DISABLE`| Disable the `BackwardsCompatibilityInterceptor`|`true`|
120
120
|`no.proxy` / `NO_PROXY`| comma-separated list of domain extensions [proxy](http://www.gnu.org/software/wget/manual/html_node/Proxies.html) should not be used for ||
121
+
|`http.proxy` / `HTTP_PROXY`| URL to the [proxy](http://www.gnu.org/software/wget/manual/html_node/Proxies.html) for HTTP requests (See [Proxy precedence](./doc/FAQ.md#how-does-kubernetesclient-loads-proxy-url-from-various-sources)) ||
122
+
|`https.proxy` / `HTTPS_PROXY`| URL to the [proxy](http://www.gnu.org/software/wget/manual/html_node/Proxies.html) for HTTPS requests (See [Proxy precedence](./doc/FAQ.md#how-does-kubernetesclient-loads-proxy-url-from-various-sources)) ||
121
123
122
124
Alternatively you can use the `ConfigBuilder` to create a config object for the Kubernetes client:
-`HTTP_PROXY` : Should be used for HTTP requests (when Kubernetes ApiServer is serving plain HTTP requests)
120
+
-`HTTPS_PROXY` : Should be used for HTTPS requests (when Kubernetes ApiServer is serving HTTPS)
121
+
122
+
URLs with `http`, `https`, and `socks5` schemes are supported.
123
+
113
124
### Optimistic Locking Behavior
114
125
115
126
Unfortunately it's a little complicated as it depends on what operation you are doing - we'll work towards ensuring the Javadocs are as informative as possible. Here is quick overview:
0 commit comments