Update to use master node IPs (verified configuration) (#510)

SUSE · Jul 19, 2019 · c8c7cd5 · c8c7cd5
1 parent 13179e7
commit c8c7cd5
Show file tree

Hide file tree

Showing 2 changed files with 6 additions and 5 deletions.
diff --git a/xml/cap_depl_install_caasp.xml b/xml/cap_depl_install_caasp.xml
@@ -100,7 +100,7 @@
       </listitem>
       <listitem>
        <para>
-        Traffic inside of &productname; resolves to a &kube; worker node in
+        Traffic inside of &productname; resolves to a &kube; master node in
         that dedicated domain.
        </para>
       </listitem>
@@ -509,11 +509,11 @@ persistentvolumeclaim "test-sc-persistent" deleted</screen>
   <para>
    The example <filename>scf-config-values.yaml</filename> file is for a simple
    deployment without an ingress controller or external load balancer. Instead, 
-   assign one worker node an external IP address, and map this to the domain 
+   assign the master node an external IP address, and map this to the domain 
    name to provide external access to the cluster. The 
    <literal>external_ips</literal> parameter needs 
    this address to provide access to the Stratos Web interface and other public
-   servers, and it needs the internal IP addresses of the worker nodes to provide 
+   servers, and it also needs the internal IP addresses of the master node to provide 
    access to internal services.
 </para>   
 
@@ -529,7 +529,8 @@ env:
   UAA_PORT: 2793
 
 kube:
-  external_ips: ["<replaceable>&kubeip;</replaceable>", "<replaceable>&subnetI;</replaceable>", "<replaceable>&subnetII;</replaceable>", "<replaceable>&subnetIII;</replaceable>"]
+  # Specify the master node's external IP and internal IP
+  external_ips: ["<replaceable>&kubeip;</replaceable>", "<replaceable>&subnetI;</replaceable>"]
 
   storage_class:
     persistent: <replaceable>"persistent"</replaceable>

diff --git a/xml/cap_depl_stratos.xml b/xml/cap_depl_stratos.xml
@@ -28,7 +28,7 @@
 
    <para>
       The steps in this section describe how to install Stratos on &susecaaspreg;
-      without an external load balancer, instead mapping a worker node to your
+      without an external load balancer, instead mapping the master node to your
       &productname; domain as described in 
       <xref linkend="sec.cap.configure-prod"/>. These instructions assume you 
       have followed the procedure in <xref linkend="cha.cap.depl-caasp"/>,