openstack/openstack-helm
Code Issues Proposed changes

Update proxy documentation for AIO

Browse Source 
This change adds in information about overriding the dns entries
that can end up overwriting the existing ones in resolv.conf
and resulting in a lack of network connectivity when deploying
AIO behind a proxy.

Change-Id: I9faab36a114e28fe8f4c312e7cd64a582333033b
This commit is contained in:
Gage Hugo
2019-12-12 13:32:36 -06:00
parent 52c132b935
commit 13b0a3ffd9
1 changed files with 12 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files

12
doc/source/install/common-requirements.rst
View File

@@ -56,3 +56,15 @@ variables.
export no_proxy=${no_proxy},172.17.0.1,.svc.cluster.local export no_proxy=${no_proxy},172.17.0.1,.svc.cluster.local
export NO_PROXY=${NO_PROXY},172.17.0.1,.svc.cluster.local export NO_PROXY=${NO_PROXY},172.17.0.1,.svc.cluster.local
By default, this installation will use Google DNS Server IPs (8.8.8.8, 8.8.4.4)
and will update resolv.conf as a result. If those IPs are blocked by the proxy,
this will overwrite the original DNS entries and result in the inability to
connect to anything on the network behind the proxy. These DNS nameserver entries
can be changed by updating the ``external_dns_nameservers`` entry in this file:
.. code-block:: bash
openstack-helm-infra/tools/images/kubeadm-aio/assets/opt/playbooks/vars.yaml
It is recommended to add your own existing DNS nameserver entries to avoid
losing connection.