Browse Source

Comment cloud providers private networks use cases

Signed-off-by: Bogdan Dobrelya <bogdando@mail.ru>
pull/845/head v2.0.1
Bogdan Dobrelya 7 years ago
parent
commit
031cf565ec
1 changed files with 5 additions and 1 deletions
  1. 6
      docs/vars.md

6
docs/vars.md

@ -33,7 +33,7 @@ Some variables of note include:
* *ip* - IP to use for binding services (host var) * *ip* - IP to use for binding services (host var)
* *access_ip* - IP for other hosts to use to connect to. Often required when * *access_ip* - IP for other hosts to use to connect to. Often required when
deploying from a cloud, such as OpenStack or GCE and you have separate
deploying from a cloud, such as OpenStack or GCE and you have separate
public/floating and private IPs. public/floating and private IPs.
* *ansible_default_ipv4.address* - Not Kargo-specific, but it is used if ip * *ansible_default_ipv4.address* - Not Kargo-specific, but it is used if ip
and access_ip are undefined and access_ip are undefined
@ -67,6 +67,10 @@ following default cluster paramters:
* *kube_hostpath_dynamic_provisioner* - Required for use of PetSets type in * *kube_hostpath_dynamic_provisioner* - Required for use of PetSets type in
Kubernetes Kubernetes
Note, if cloud providers have any use of the ``10.233.0.0/16``, like instances'
private addresses, make sure to pick another values for ``kube_service_addresses``
and ``kube_pods_subnet``, for example from the ``172.18.0.0/16``.
#### DNS variables #### DNS variables
By default, dnsmasq gets set up with 8.8.8.8 as an upstream DNS server and all By default, dnsmasq gets set up with 8.8.8.8 as an upstream DNS server and all

Loading…
Cancel
Save