|
| 1 | +--- |
| 2 | +title: "Copy the following example |onprem| |k8s| |k8s-obj|." |
| 3 | +stepnum: 1 |
| 4 | +level: 4 |
| 5 | +ref: copy-k8s-example |
| 6 | +content: | |
| 7 | +
|
| 8 | + Change the highlighted settings to match your desired |
| 9 | + |onprem| configuration. |
| 10 | +
|
| 11 | + .. literalinclude:: /reference/k8s/example-opsmgr-minimal.yaml |
| 12 | + :language: yaml |
| 13 | + :emphasize-lines: 5-10,12-13 |
| 14 | +
|
| 15 | +--- |
| 16 | +title: "Open your preferred text editor and paste the |k8s-obj| specification into a new text file." |
| 17 | +stepnum: 2 |
| 18 | +level: 4 |
| 19 | +ref: paste-k8s-example |
| 20 | +--- |
| 21 | +title: "Configure the settings highlighted in the prior example." |
| 22 | +stepnum: 3 |
| 23 | +level: 4 |
| 24 | +ref: change-k8s-values |
| 25 | +content: | |
| 26 | +
|
| 27 | + .. list-table:: |
| 28 | + :widths: 20 20 40 20 |
| 29 | + :header-rows: 1 |
| 30 | +
|
| 31 | + * - Key |
| 32 | + - Type |
| 33 | + - Description |
| 34 | + - Example |
| 35 | +
|
| 36 | + * - :opsmgrkube:`metadata.name` |
| 37 | + - string |
| 38 | + - Name for this |k8s| |onprem| |k8s-obj|. |
| 39 | +
|
| 40 | + .. seealso:: |
| 41 | +
|
| 42 | + - :opsmgrkube:`metadata.name` |
| 43 | + - |k8s| documentation on :k8sdocs:`names </concepts/overview/working-with-objects/names/>`. |
| 44 | +
|
| 45 | + - ``om`` |
| 46 | +
|
| 47 | + * - :opsmgrkube:`spec.version` |
| 48 | + - string |
| 49 | + - Version of |onprem| to be installed. |
| 50 | +
|
| 51 | + The format should be :manual:`X.Y.Z </reference/versioning>`. |
| 52 | + To view available |onprem| versions, view the |
| 53 | + `container registry <https://quay.io/repository/mongodb/mongodb-enterprise-ops-manager?tag=latest&tab=tags>`__. |
| 54 | + - ``4.2.0`` |
| 55 | +
|
| 56 | + * - :opsmgrkube:`spec.adminCredentials` |
| 57 | + - string |
| 58 | + - Name of the |k8s-secret| you :ref:`created <om-rsrc-prereqs>` |
| 59 | + for the |onprem| admin user. |
| 60 | +
|
| 61 | + .. note:: |
| 62 | +
|
| 63 | + Configure the secret to use the same |k8s-ns| as the |onprem| |
| 64 | + resource. |
| 65 | + |
| 66 | + - ``om-admin-secret`` |
| 67 | +
|
| 68 | + * - | ``spec`` |
| 69 | + | ``.applicationDatabase`` |
| 70 | + | ``.``:setting:`~spec.members` |
| 71 | + - integer |
| 72 | + - Number of members of the :ref:`mms-application-database` |
| 73 | + replica set. |
| 74 | + - ``3`` |
| 75 | +
|
| 76 | + * - | ``spec`` |
| 77 | + | ``.applicationDatabase`` |
| 78 | + | ``.``:setting:`~spec.version` |
| 79 | + - string |
| 80 | + - Version of MongoDB that the :ref:`mms-application-database` |
| 81 | + should run. |
| 82 | + |
| 83 | + The format should be ``X.Y.Z`` for the Community edition and |
| 84 | + ``X.Y.Z-ent`` for the :product:`Enterprise edition |
| 85 | + </mongodb-enterprise-advanced>`. |
| 86 | +
|
| 87 | + To learn more about MongoDB versioning, see see |
| 88 | + :ref:`release-version-numbers` in the MongoDB Manual. |
| 89 | + - ``4.0.7`` |
| 90 | +
|
| 91 | + * - | ``spec`` |
| 92 | + | ``.applicationDatabase`` |
| 93 | + | ``.``:setting:`~spec.persistent` |
| 94 | + - boolean |
| 95 | + - *Optional.* |
| 96 | +
|
| 97 | + Flag indicating if this |k8s-mdbrsc| should use |k8s-pvs| for |
| 98 | + storage. Persistent volumes are not deleted when the |
| 99 | + |k8s-mdbrsc| is stopped or restarted. |
| 100 | +
|
| 101 | + If this value is ``true``, then |
| 102 | + ``spec.applicationDatabase.podSpec.persistence.`` |
| 103 | + :setting:`~spec.podSpec.persistence.single` |
| 104 | + is set to its default value of ``16G``. |
| 105 | +
|
| 106 | + To change your |k8s-pvcs| configuration, configure the |
| 107 | + following collections to meet your deployment requirements: |
| 108 | +
|
| 109 | + - If you want one |k8s-pv| for each |k8s-pod|, configure the |
| 110 | + ``spec.applicationDatabase.`` |
| 111 | + :setting:`~spec.podSpec.persistence.single` collection. |
| 112 | +
|
| 113 | + - If you want separate |k8s-pvs| for data, journals, and |
| 114 | + logs for each |k8s-pod|, configure the following |
| 115 | + collections: |
| 116 | +
|
| 117 | + - | ``spec.applicationDatabase`` |
| 118 | + | ``.podSpec.persistence.multiple.`` |
| 119 | + | :setting:`~spec.podSpec.persistence.multiple.data` |
| 120 | + - | ``spec.applicationDatabase`` |
| 121 | + | ``.podSpec.persistence.multiple.`` |
| 122 | + | :setting:`~spec.podSpec.persistence.multiple.journal` |
| 123 | + - | ``spec.applicationDatabase`` |
| 124 | + | ``.podSpec.persistence.multiple.`` |
| 125 | + | :setting:`~spec.podSpec.persistence.multiple.logs` |
| 126 | +
|
| 127 | + .. include:: /includes/k8s/k8s-persistent-volumes-om.rst |
| 128 | +
|
| 129 | + - ``true`` |
| 130 | +
|
| 131 | +--- |
| 132 | +title: "(Optional) Configure any additional settings for an |onprem| deployment." |
| 133 | +stepnum: 4 |
| 134 | +level: 4 |
| 135 | +ref: add-k8s-values |
| 136 | +content: | |
| 137 | + |
| 138 | + You can add any of the following optional settings to the |
| 139 | + |k8s-obj| specification file for an |onprem| deployment: |
| 140 | +
|
| 141 | + - :opsmgrkube:`spec.clusterName` |
| 142 | + - :opsmgrkube:`spec.configuration` |
| 143 | + - ``spec.applicationDatabase.``:setting:`~spec.logLevel` |
| 144 | + - ``spec.applicationDatabase.``:setting:`~spec.featureCompatibilityVersion` |
| 145 | + - ``spec.applicationDatabase.podSpec.``:setting:`~spec.podSpec.cpu` |
| 146 | + - ``spec.applicationDatabase.podSpec.``:setting:`~spec.podSpec.cpuRequests` |
| 147 | + - ``spec.applicationDatabase.podSpec.``:setting:`~spec.podSpec.memory` |
| 148 | + - ``spec.applicationDatabase.podSpec.``:setting:`~spec.podSpec.memoryRequests` |
| 149 | + - ``spec.applicationDatabase.podSpec.persistence.``:setting:`~spec.podSpec.persistence.single` |
| 150 | + - ``spec.applicationDatabase.podSpec.persistence.multiple.``:setting:`~spec.podSpec.persistence.multiple.data` |
| 151 | + - ``spec.applicationDatabase.podSpec.persistence.multiple.``:setting:`~spec.podSpec.persistence.multiple.journal` |
| 152 | + - ``spec.applicationDatabase.podSpec.persistence.multiple.``:setting:`~spec.podSpec.persistence.multiple.logs` |
| 153 | + - ``spec.applicationDatabase.podSpec.``:setting:`~spec.podSpec.podAffinity` |
| 154 | + - ``spec.applicationDatabase.podSpec.``:setting:`~spec.podSpec.podAntiAffinityTopologyKey` |
| 155 | + - ``spec.applicationDatabase.podSpec.``:setting:`~spec.podSpec.nodeAffinity` |
| 156 | +
|
| 157 | +--- |
| 158 | +title: "Save this file with a ``.yaml`` file extension." |
| 159 | +stepnum: 5 |
| 160 | +level: 4 |
| 161 | +ref: save-object-spec |
| 162 | + |
| 163 | +--- |
| 164 | +title: "Create your |onprem| instance." |
| 165 | +stepnum: 6 |
| 166 | +level: 4 |
| 167 | +ref: start-k8s-instance |
| 168 | +content: | |
| 169 | +
|
| 170 | + Invoke the following ``kubectl`` command on the filename of the |
| 171 | + |onprem| resource definition: |
| 172 | +
|
| 173 | + .. code-block:: sh |
| 174 | +
|
| 175 | + kubectl apply -f <opsmgr-resource>.yaml |
| 176 | +
|
| 177 | +--- |
| 178 | +title: "Track the status of your |onprem| instance." |
| 179 | +stepnum: 7 |
| 180 | +level: 4 |
| 181 | +ref: track-k8s-instance |
| 182 | +content: | |
| 183 | +
|
| 184 | + To check the status of your |onprem| resource, invoke the following |
| 185 | + command: |
| 186 | +
|
| 187 | + .. code-block:: sh |
| 188 | +
|
| 189 | + kubectl get om -n <namespace> -o yaml -w |
| 190 | + |
| 191 | + The ``-w`` flag means "watch". With the "watch" flag set, the output |
| 192 | + refreshes immediately when something changes. |
| 193 | +
|
| 194 | + If the deployment fails, see :doc:`/reference/troubleshooting`. |
| 195 | +
|
| 196 | +--- |
| 197 | +title: "Access your |onprem| instance from a browser." |
| 198 | +stepnum: 8 |
| 199 | +level: 4 |
| 200 | +ref: access-opsmgr-instance |
| 201 | +content: | |
| 202 | + |
| 203 | + a. After the resource deploys successfully, find the external port to |
| 204 | + your |onprem| instance. |
| 205 | + |
| 206 | + Invoke the following ``kubectl`` command on ``<metadata.name>-svc-external``: |
| 207 | + ``metadata.name`` : |
| 208 | +
|
| 209 | + .. code-block:: sh |
| 210 | +
|
| 211 | + kubectl get svc <metadata.name>-svc-external -n <namespace> |
| 212 | +
|
| 213 | + The command returns the external port in the ``PORT(S)`` column. In |
| 214 | + the following example output, the external port is ``30036``: |
| 215 | +
|
| 216 | + .. code-block:: sh |
| 217 | + :copyable: false |
| 218 | +
|
| 219 | + NAME TYPE CLUSTER-IP EXTERNAL-IP PORT(S) AGE |
| 220 | + <metadata.name>-svc-external NodePort 100.66.92.110 <none> 8080:30036/TCP 1d |
| 221 | + |
| 222 | + #. Set your firewall rules to allow access from the Internet to the |
| 223 | + external port on the host. |
| 224 | +
|
| 225 | + #. Open a browser window and navigate to the |onprem| application |
| 226 | + using the |fqdn| and port number. |
| 227 | +
|
| 228 | + .. code-block:: sh |
| 229 | +
|
| 230 | + http://ops.example.com:30036 |
| 231 | + |
| 232 | + #. Log in to |onprem| using the :ref:`admin user credentials |
| 233 | + <om-rsrc-prereqs>`. |
| 234 | +... |
0 commit comments