(DOCSP-13793): can't update mdbagent version using om (#464)

* (DOCSP-13793): can't update mdbagent version using om

* (DOCSP-13793): adding links to new operator settings

Author: jwilliams-mongo

source/reference/helm-operator-settings.txt

@@ -180,6 +180,8 @@ registry.appDb
             registry:
               appDb: registry.connect.redhat.com/mongodb
 
+.. _registry-appdb-version:
+
 registry.appDb.version
 ----------------------
 

source/reference/known-issues.txt

@@ -113,6 +113,23 @@ automatically and starts working correctly:
 
       :doc:`Kubernetes Operator installation </tutorial/install-k8s-operator>`
 
+.. _unable-to-upgrade-appdb-agent-in-om:
+
+Unable to Update the {+mdbagent+} on Application Database Pods
+-----------------------------------------------------------------
+
+You can't use |onprem| to upgrade the {+mdbagent+}\s that run on the
+Application Database Pods. The {+mdbagent+} version that runs on these
+Pods is embedded in the Application Database Docker image.
+
+You can use the |k8s-op-short| to upgrade the {+mdbagent+} version on
+Application Database Pods as MongoDB publishes new images.
+
+.. seealso::
+
+   - :ref:`meko-appdb-agent-version`
+   - :ref:`registry-appdb-version`
+
 Machine Memory vs. Container Memory
 -----------------------------------
 

source/reference/kubectl-operator-settings.txt

@@ -46,6 +46,8 @@ add it as a new array of key-value pair mappings in the
                   - name: APPDB_IMAGE_REPOSITORY
                     value: quay.io/mongodb/mongodb-enterprise-appdb
 
+.. _meko-appdb-agent-version:
+
 APPDB_AGENT_VERSION
 -------------------