(DOCSP-8046): add externalconnectivity to opsmgr sample (#166)

* (DOCSP-8046): add externalconnectivity to opsmgr sample

* (DOCSP-8046): copy review feedback

* (DOCSP-8046): tech review feedback

Author: jwilliams-mongo

source/includes/steps-deploy-k8s-opsmgr.yaml

@@ -11,7 +11,7 @@ content: |
    .. literalinclude:: /reference/k8s/example-opsmgr-minimal.yaml
       :language: yaml
       :linenos:
-      :emphasize-lines: 5,7-11,13,15,17-19,21,23-25,27-31,34-35
+      :emphasize-lines: 5,7-11,13,15,17-19,21,23-25,27-31,34,38-39
 
 ---
 title: "Open your preferred text editor and paste the |k8s-obj| specification into a new text file."
@@ -152,6 +152,26 @@ content: |
           database Backup snapshots.
         - my-bucket
 
+      * - | ``spec``
+          | ``.externalConnectivity``
+          | ``.``:opsmgrkube:`~spec.externalConnectivity.type`
+        - string
+        - *Optional*.
+
+          The |k8s| service :k8sdocs:`ServiceType 
+          </concepts/services-networking/service/#publishing-services-service-types>` 
+          that exposes |onprem| outside of |k8s|.
+
+          .. note::
+
+             Exclude the ``spec.``:opsmgrkube:`~spec.externalConnectivity`
+             setting and its children if you don't want the 
+             |k8s-op-short| to create a |k8s| service to route external 
+             traffic to the |onprem| application.
+
+
+        - ``LoadBalancer``        
+
       * - | ``spec``
           | ``.applicationDatabase`` 
           | ``.``:setting:`~spec.members`
@@ -214,48 +234,10 @@ content: |
           .. include:: /includes/k8s/k8s-persistent-volumes-om.rst
 
         - ``true``
----
-title: "Allow external traffic to reach the |onprem| application."
-stepnum: 4
-level: 4
-ref: om-external-connectivity
-content: |
-  
-  By default, the |k8s-op-short| does not create a |k8s| service to 
-  route traffic originating from outside of the |k8s| cluster to the 
-  |onprem| application.
-
-  To access the |onprem| application, you can:
-  
-  - Configure the |k8s-op-short| to create a |k8s| service.
-  - Create a |k8s| service manually. MongoDB recommends using a 
-    ``LoadBalancer`` |k8s| service if your cloud provider supports it.
-  - If you're using OpenShift, use 
-    `Routes <https://docs.openshift.com/enterprise/3.0/architecture/core_concepts/routes.html>`__.
-  - Use a third-party service, such as Istio.
-
-  The simplest method is to configure the |k8s-op-short| to create a 
-  |k8s| service to route external traffic to the |onprem| application:
-
-  a. Add the ``spec.``:opsmgrkube:`~spec.externalConnectivity` setting 
-     to the |k8s-obj| specification.
-
-  #. Add the following settings to the |k8s-obj| specification 
-     to configure the |k8s| service that routes external traffic to the 
-     |onprem| application:
-
-     - ``spec.externalConnectivity.``:opsmgrkube:`~spec.externalConnectivity.type`
-     - (optional) ``spec.externalConnectivity.``:opsmgrkube:`~spec.externalConnectivity.port`
-
-  To learn how to create a |k8s| :k8sdocs:`service </concepts/services-networking/service/>`
-  manually, see the |k8s| documentation.
-
-  To learn how to route external traffic to the |onprem| application 
-  using a different method, refer to the documentation for your solution.
 
 ---
 title: "(Optional) Configure any additional settings for an |onprem| deployment."
-stepnum: 5
+stepnum: 4
 level: 4
 ref: add-k8s-values
 content: |
@@ -286,16 +268,20 @@ content: |
   - ``spec.backup.opLogStores.mongodbUserRef.``:opsmgrkube:`~spec.backup.opLogStores.mongodbUserRef.name`
   - ``spec.backup.s3Stores.mongodbUserRef.``:opsmgrkube:`~spec.backup.s3Stores.mongodbUserRef.name`
   - ``spec.backup.s3Stores.``:opsmgrkube:`~spec.backup.s3Stores.pathStyleAccessEnabled`
+  - ``spec.externalConnectivity.``:opsmgrkube:`~spec.externalConnectivity.port`
+  - ``spec.externalConnectivity.``:opsmgrkube:`~spec.externalConnectivity.loadBalancerIP`
+  - ``spec.externalConnectivity.``:opsmgrkube:`~spec.externalConnectivity.externalTrafficPolicy`
+  - ``spec.externalConnectivity.``:opsmgrkube:`~spec.externalConnectivity.annotations`
 
 ---
 title: "Save this file with a ``.yaml`` file extension."
-stepnum: 6
+stepnum: 5
 level: 4
 ref: save-object-spec
 
 ---
 title: "Create your |onprem| instance."
-stepnum: 7
+stepnum: 6
 level: 4
 ref: start-k8s-instance
 content: |
@@ -309,7 +295,7 @@ content: |
 
 ---
 title: "Track the status of your |onprem| instance."
-stepnum: 8
+stepnum: 7
 level: 4
 ref: track-k8s-instance
 content: |
@@ -372,7 +358,7 @@ content: |
 
 ---
 title: "Access the |onprem| application."
-stepnum: 9
+stepnum: 8
 level: 4
 ref: access-opsmgr-instance
 content: |
@@ -422,8 +408,8 @@ content: |
         
         #. Log in to |onprem| using the :ref:`admin user credentials <om-rsrc-prereqs>`.
 
-  To learn how to access the |onprem| application using a different 
-  traffic routing method, refer to the documentation for your solution.
+  To learn how to access the |onprem| application using a third-party 
+  service, refer to the documentation for your solution.
   
 ---
 title: "Create credentials for the Kubernetes Operator."

source/reference/k8s/example-opsmgr-minimal.yaml

@@ -30,6 +30,9 @@ spec:
         s3BucketEndpoint: <s3.region.amazonaws.com>
         s3BucketName: <bucketname>
 
+  externalConnectivity:
+    type: LoadBalancer
+
   applicationDatabase:
     members: 3
     version: <mongodbversion>

source/tutorial/deploy-om-container.txt

@@ -27,7 +27,7 @@ Prerequisites
 
 To deploy an |onprem| resource you must:
 
-1. :doc:`Install </tutorial/install-k8s-operator>` the |k8s-op| 1.3.0
+1. :doc:`Install </tutorial/install-k8s-operator>` the |k8s-op| 1.4.1
    or newer.
 
 #. Ensure that the host on which you want to deploy |onprem| has a
@@ -225,7 +225,32 @@ To configure an |s3| :opsmgr:`snapshot store
 
 You can update any additional |s3| :opsmgr:`configuration settings
 </tutorial/manage-s3-blockstore-storage/#provide-the-s3-blockstore-details>`
-that are not managed by the |k8s-op-short| through the |application|. 
+that are not managed by the |k8s-op-short| through the |application|.
+
+Ops Manager Application Access
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+
+By default, the |k8s-op-short| does not create a |k8s| service to route 
+traffic originating from outside of the |k8s| cluster to the |onprem| 
+application.
+
+To access the |onprem| application, you can:
+
+- Configure the |k8s-op-short| to create a |k8s| service.
+- Create a |k8s| service manually. MongoDB recommends using a 
+  ``LoadBalancer`` |k8s| service if your cloud provider supports it.
+- If you're using OpenShift, use 
+  `routes <https://docs.openshift.com/enterprise/3.0/architecture/core_concepts/routes.html>`__.
+- Use a third-party service, such as Istio.
+
+The simplest method is configuring the |k8s-op-short| to create a |k8s| 
+service that routes external traffic to the |onprem| application. The 
+|onprem| deployment procedure instructs you to add the following 
+settings to the |k8s-obj| specification that configures the |k8s-op-short| 
+to create a service:
+
+- ``spec.``:opsmgrkube:`~spec.externalConnectivity`
+- ``spec.externalConnectivity.``:opsmgrkube:`~spec.externalConnectivity.type`
 
 Procedure
 ---------