c12s-kubespray/docs/proxy.md

# Setting up Environment Proxy

If you set http and https proxy, all nodes and loadbalancer will be excluded from proxy with generating no_proxy variable in `roles/kubespray-defaults/tasks/no_proxy.yml`, if you have additional resources for exclude add them to `additional_no_proxy` variable. If you want fully override your `no_proxy` setting, then fill in just `no_proxy` and no nodes or loadbalancer addresses will be added to no_proxy.

## Set proxy for http and https

 `http_proxy:"http://example.proxy.tld:port"`
 `https_proxy:"http://example.proxy.tld:port"`

## Set default no_proxy (this will override default no_proxy generation)

`no_proxy: "node1,node1_ip,node2,node2_ip...additional_host"`

## Set additional addresses to default no_proxy (all cluster nodes and loadbalancer)

`additional_no_proxy: "aditional_host1,aditional_host2"`

## Exclude workers from no_proxy

Since workers are included in the no_proxy variable, by default, docker engine will be restarted on all nodes (all
pods will restart) when adding or removing workers.  To override this behaviour by only including master nodes in the
no_proxy variable, set:
`no_proxy_exclude_workers: true`
Add additional no proxy parameter for more customization 2018-08-24 07:28:29 +00:00			`# Setting up Environment Proxy`

assembly fallback_ips and no_proxy var only one time on localhost and… (#5957) * assembly fallback_ips and no_proxy var only one time on localhost and populate result on all hosts * add tag always, fix ansible lint errors * workaround to mitogen issue dw/mitogen#663 * do not gather fact before install python on coreos like distros * try to pass docker molecule test 2020-04-16 14:22:47 +00:00			If you set http and https proxy, all nodes and loadbalancer will be excluded from proxy with generating no_proxy variable in `roles/kubespray-defaults/tasks/no_proxy.yml`, if you have additional resources for exclude add them to `additional_no_proxy` variable. If you want fully override your `no_proxy` setting, then fill in just `no_proxy` and no nodes or loadbalancer addresses will be added to no_proxy.
Add additional no proxy parameter for more customization 2018-08-24 07:28:29 +00:00
			`## Set proxy for http and https`

			`http_proxy:"http://example.proxy.tld:port"`
			`https_proxy:"http://example.proxy.tld:port"`

			`## Set default no_proxy (this will override default no_proxy generation)`

			`no_proxy: "node1,node1_ip,node2,node2_ip...additional_host"`

			`## Set additional addresses to default no_proxy (all cluster nodes and loadbalancer)`

Proxy small fixes (#7102) * Improve how we set 'proxy=' in yum.conf or dnf.conf Signed-off-by: Etienne Champetier <champetier.etienne@gmail.com> * Fixup spaces in no_proxy Signed-off-by: Etienne Champetier <champetier.etienne@gmail.com> * Add svc,svc.{{ dns_domain }} to no_proxy Signed-off-by: Etienne Champetier <champetier.etienne@gmail.com> 2021-01-07 18:50:53 +00:00			`additional_no_proxy: "aditional_host1,aditional_host2"`
If no_proxy_exclude_workers is true, workers will be excluded from the no_proxy variable. This prevents docker engine restarting when scaling workers. (#6520) Signed-off-by: holmesb <5072156+holmesb@users.noreply.github.com> 2020-10-09 08:15:07 +00:00
			`## Exclude workers from no_proxy`

			`Since workers are included in the no_proxy variable, by default, docker engine will be restarted on all nodes (all`
			`pods will restart) when adding or removing workers. To override this behaviour by only including master nodes in the`
			`no_proxy variable, set:`
			`no_proxy_exclude_workers: true`