Extend network and K8S installation instructions
Add minor details to K8s installation steps
Drop repeat of ric-infra and ric-plt from ric-aux,
add large resource requirements
Signed-off-by: Lott, Christopher (cl778h) <cl778h@att.com>
Change-Id: Ib787fb678a4e114a23c0a7ef144524b23ab3d1d5
diff --git a/docs/installation-guides.rst b/docs/installation-guides.rst
index f451c81..6f734a0 100644
--- a/docs/installation-guides.rst
+++ b/docs/installation-guides.rst
@@ -51,7 +51,9 @@
.. image:: images/nrtric-amber.png
:width: 600
-Within the RIC cluster, Kubernetes resources are deployed using three name spaces: ricinfra, ricplt, and ricxapp. Similarly, within the AUX cluster, Kubernetes resources are deployed using two name spaces: ricinfra, and ricaux.
+Within the RIC cluster, Kubernetes resources are deployed using three name spaces: ricinfra, ricplt,
+and ricxapp. Similarly, within the AUX cluster, Kubernetes resources are deployed using two name spaces:
+ricinfra, and ricaux.
For each cluster, there is a Kong ingress controller that proxies incoming API calls into the cluster.
With Kong, service APIs provided by Kubernetes resources can be accessed at the cluster node IP and