From 031cf565ec3ccd3ebbe80eeef3454c3780e5c598 Mon Sep 17 00:00:00 2001
From: Bogdan Dobrelya <bogdando@mail.ru>
Date: Mon, 2 Jan 2017 11:40:56 +0100
Subject: [PATCH] Comment cloud providers private networks use cases

Signed-off-by: Bogdan Dobrelya <bogdando@mail.ru>
---
 docs/vars.md | 6 +++++-
 1 file changed, 5 insertions(+), 1 deletion(-)

diff --git a/docs/vars.md b/docs/vars.md
index 2bed6f28c..c904e9336 100644
--- a/docs/vars.md
+++ b/docs/vars.md
@@ -33,7 +33,7 @@ Some variables of note include:
 
 * *ip* - IP to use for binding services (host var)
 * *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.
 * *ansible_default_ipv4.address* - Not Kargo-specific, but it is used if ip
   and access_ip are undefined
@@ -67,6 +67,10 @@ following default cluster paramters:
 * *kube_hostpath_dynamic_provisioner* - Required for use of PetSets type in
   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
 
 By default, dnsmasq gets set up with 8.8.8.8 as an upstream DNS server and all
-- 
GitLab