Skip to content

Commit 3d0ab20

Browse files
kanchana-mongodbjwilliams-mongo
authored andcommitted
DOCSP-17302 fix for Errors in Kubernetes Ops Manager page (#640)
1 parent 69fb56c commit 3d0ab20

File tree

1 file changed

+5
-4
lines changed

1 file changed

+5
-4
lines changed

source/tutorial/om-arch.txt

Lines changed: 5 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -47,16 +47,17 @@ For the Application Database, the |k8s-op-short| deploys a MongoDB
4747
replica set as a |k8s-statefulset| to the |k8s| cluster. |k8s| creates
4848
one Pod in the StatefulSet for each member
4949
that comprises your Application Database replica set. Each Pod in
50-
the StatefulSet runs a ``mongod`` and the {+mdbagent}.
50+
the StatefulSet runs a ``mongod`` and the {+mdbagent+}.
5151

5252
To enable each {+mdbagent+} to start |mongod| on its
5353
Pod in the StatefulSet, you must specify a specific MongoDB Server
5454
version for the Application Database using the
5555
:opsmgrkube:`spec.applicationDatabase.version` setting. The version
5656
that you specify in this setting must correspond to the tag in the
57-
:qr-mdb: `container registry </mongodb-enterprise-appdb-database?tab=tags>`.
58-
Each {+mdbagent+} starts the Application Database with the specified
59-
version on its Pod in the StatefulSet.
57+
:qr-mdb:`container registry
58+
</mongodb-enterprise-appdb-database?tab=tags>`. Each {+mdbagent+}
59+
starts the Application Database with the specified version on its Pod
60+
in the StatefulSet.
6061

6162
After each {+mdbagent+} starts |mongod|\s on its Application Database
6263
Pod, the {+mdbagent+}\s add all |mongod| processes to the Application

0 commit comments

Comments
 (0)