airship/charts
Code Issues Proposed changes
charts/doc/source/install/jarvis/proxy.rst
Dustin Specker c3f2887afb docs(install/jarvis/vagrant): update hosts and add notes 
- add tekton.jarvis.local to /etc/hosts

- add info about Windows hosts file

- add note about multiple nameservers

Since systemd-resolved is being used, we can leverage that configuration
to support multiple nameservers by simply passing in a space separated
value [1].

1 - https://www.freedesktop.org/software/systemd/man/resolved.conf.html#DNS=

Change-Id: I252da348c8e31d6c322ac0acac4bc500a8f741a8
2021-03-02 16:32:04 -06:00

2.0 KiB
Raw Blame History

Running Jarvis Behind Corporate Proxy

Environment Variables

On the host machine, ensure the following environment variables are set with the appropriate proxy information: HTTP_PROXY, HTTPS_PROXY, and NO_PROXY. You will also need to set the environment variable PRIVATE_NS to an IP address of a corporate name server that will resolve internal URLs. PRIVATE_NS can support multiple corporate name servers by creating a space separated list, such as PRIVATE_NS="172.18.0.17 172.19.0.17".

Vagrant Plugin

To easily set up the Vagrant box's proxy setting, install the vagrant_proxyconf plugin by running:

$ vagrant plugin install vagrant-proxyconf

NO_PROXY Configuration

In the event NO_PROXY is not specified, the following default value will be used:

localhost,127.0.0.1,10.96.0.0/12,192.168.49.0/24,192.168.99.0/24,10.0.2.15,10.244.0.0/16,172.28.0.0/30,.minikube.internal,.svc,.svc.cluster.local,jarvis.local

Please note the following will need to be accounted for to avoid traffic being routed through the proxy:

  • Localhost: localhost and 127.0.0.1,
  • Host and guest machine IP and name: jarvis, jarvis.local, etc.,
  • Minikube specific IP ranges (e.g. 102.168.49.0/24). See minikube's documentation for detail,
  • Minikube places host.minikube.internal and control-plane.minikube.internal into /etc/hosts,
  • Kubernetes services' URLs with ending of .svc, .cluster.local or .svc.cluster.local,
  • Kubernetes service cluster IP ranges: 10.96.0.0/12 or what's configured via --service-cluster-ip-range.
  • DNSMasq subnet range: 172.28.0.0/30

Installation

With the appropriate environment variables set, follow instruction here <aio-installation>.