Added spec.backup.members (#645)

* Added spec.backup.members

* Included tech review from Nik

* Replaced refs to OM /rapid releases, added one more link, fixed a typo

* Final link cleanup

Author: JuliaMongo

config/intersphinx.yaml

@@ -21,8 +21,5 @@ path: biconnector.inv
 name: opsmanager
 url: https://docs.opsmanager.mongodb.com/current/
 path: objects.inv
----
-name: opsmanagerrapid
-url: https://docs.opsmanager.mongodb.com/rapid/
-path: opsmgrrapid.inv
+
 ...

source/includes/admonitions/note-highly-available-om.rst

@@ -1,7 +1,9 @@
 .. admonition:: Highly Available Ops Manager Resources
    :class: note
 
-   For high availability, set this value to more than ``1``. Multiple
-   |onprem| instances can read from the same Application
-   Database, ensuring failover if one instance is unavailable and
-   enabling you to update the |onprem| resource without downtime.
+   For high availability, set this value to more than ``1``.
+   :opsmgr:`Multiple Ops Manager instances
+   </tutorial/configure-application-high-availability/#multiple-application-servers>`
+   can read from the same Application Database, ensuring failover if
+   one instance is unavailable and enabling you to update the
+   |onprem| resource without downtime.

source/reference/k8s-operator-om-specification.txt

@@ -66,10 +66,9 @@ resources.
 
 .. opsmgrkube:: spec.replicas
 
-   *Type*: number
+   *Type*: integer
 
    *Required*. Number of |onprem| instances to run in parallel.
-
    The minimum accepted value is ``1``.
 
    .. include:: /includes/admonitions/note-highly-available-om.rst
@@ -286,6 +285,17 @@ Optional |onprem| Resource Settings
       backup service based on the container's memory. Changing the
       ``-Xms`` and ``-Xmx`` values can cause issues with |onprem|.
 
+.. opsmgrkube:: spec.backup.members
+
+   *Type*: integer
+   
+   *Optional*. Number of :opsmgr:`backup daemon services
+   </core/system-overview/#backup-daemon-service>`
+   to deploy in |k8s|. If not specified, defaults to ``1``.
+   To ensure high availability for your backup service, deploy
+   :opsmgr:`multiple backup daemons </tutorial/configure-backup-high-availability/#multiple-backup-daemons>`
+   in |onprem|.
+   
 .. opsmgrkube:: spec.backup.opLogStores
 
    *Type*: collection
@@ -407,20 +417,22 @@ Optional |onprem| Resource Settings
    *Type*: collection
 
    Specification for the |k8s-statefulset| that the |k8s-op| creates
-   for the :ref:`backup-daemon`.
+   for the :opsmgr:`backup daemon service
+   </core/system-overview/#backup-daemon-service>`.
 
    To review which fields you can add to
    :opsmgrkube:`spec.backup.statefulSet.spec`, see the
    :k8sdocs:`Kubernetes documentation
-   </reference/generated/kubernetes-api/v1.16/#statefulsetspec-v1-apps>`.
+   </reference/generated/kubernetes-api/v1.21/#statefulsetspec-v1-apps>`.
 
 .. opsmgrkube:: spec.backup.statefulSet.spec.template
 
    *Type*: collection
 
    :k8sdocs:`Template </concepts/workloads/pods/pod-overview/#pod-templates>`
    for the |k8s| pods in the |k8s-statefulset| that the |k8s-op| creates
-   for the :ref:`backup-daemon`.
+   for the :opsmgr:`backup daemon service
+   </core/system-overview/#backup-daemon-service>`.
 
    .. note::
 
@@ -432,28 +444,31 @@ Optional |onprem| Resource Settings
    *Type*: collection
 
    Metadata for the |k8s| pods in the |k8s-statefulset| that the
-   |k8s-op| creates for the :ref:`backup-daemon`.
+   |k8s-op| creates for the :opsmgr:`backup daemon service
+   </core/system-overview/#backup-daemon-service>`.
 
    To review which fields you can add to
    :opsmgrkube:`spec.backup.statefulSet.spec.template.metadata`, see
    the :k8sdocs:`Kubernetes documentation
-   </reference/generated/kubernetes-api/v1.16/#objectmeta-v1-meta>`.
+   </reference/generated/kubernetes-api/v1.21/#objectmeta-v1-meta>`.
 
 .. opsmgrkube:: spec.backup.statefulSet.spec.template.spec
 
    *Type*: collection
 
    Specifications of the |k8s| pods in the |k8s-statefulset| that the
-   |k8s-op| creates for the :ref:`backup-daemon`.
+   |k8s-op| creates for the :opsmgr:`backup daemon service
+   </core/system-overview/#backup-daemon-service>`.
 
    To review the complete list of fields you can add to
    :opsmgrkube:`spec.backup.statefulSet.spec.template.spec`, see the
    :k8sdocs:`Kubernetes documentation
-   </reference/generated/kubernetes-api/v1.16/#podspec-v1-core>`.
+   </reference/generated/kubernetes-api/v1.21/#podspec-v1-core>`.
 
    The following example ``spec.backup.statefulSet.spec.template.spec``
    defines minimum and maximum CPU and memory capacity for one
-   :ref:`backup-daemon` container the |k8s-op| deploys:
+   :opsmgr:`backup daemon service
+   </core/system-overview/#backup-daemon-service>` container the |k8s-op| deploys:
 
    .. code-block:: yaml
 
@@ -478,9 +493,11 @@ Optional |onprem| Resource Settings
 
    List of containers that belong to the |k8s| pods in the
    |k8s-statefulset| that the |k8s-op| creates for the
-   :ref:`backup-daemon`.
+   :opsmgr:`backup daemon service
+   </current/core/system-overview/#backup-daemon-service>`.
 
-   To modify the specifications of the :ref:`backup-daemon` container,
+   To modify the specifications of the :opsmgr:`backup daemon service
+   </current/core/system-overview/#backup-daemon-service>` container,
    you must provide the exact name of the container using the ``name``
    field, as shown in the following example:
 
@@ -506,7 +523,8 @@ Optional |onprem| Resource Settings
    *Type*: string
 
    Minimum CPU capacity that must be available on a |k8s| |k8s-node| to
-   host the :ref:`backup-daemon`.
+   host the :opsmgr:`backup daemon service
+   </current/core/system-overview/#backup-daemon-service>`.
 
    The requested value must be less than or equal to
    :opsmgrkube:`spec.backup.statefulSet.spec.template.spec.containers.resources.limits.cpu`.
@@ -516,16 +534,20 @@ Optional |onprem| Resource Settings
    *Type*: string
 
    Maximum CPU capacity for the |k8s-node| being created to host
-   the :ref:`backup-daemon`. If omitted, this value is set to
+   the :opsmgr:`backup daemon service
+   </current/core/system-overview/#backup-daemon-service>`.
+   If omitted, this value is set to
    :opsmgrkube:`spec.backup.statefulSet.spec.template.spec.containers.resources.requests.cpu`.
 
 .. opsmgrkube:: spec.backup.statefulSet.spec.template.spec.containers.resources.requests.memory
 
    *Type*: string
 
    Minimum memory capacity that must be available on a |k8s| |k8s-node|
-   to host the :ref:`backup-daemon` on |k8s|. This value is expressed as
-   an integer followed by a unit of memory in |jedec| notation.
+   to host the :opsmgr:`backup daemon service
+   </current/core/system-overview/#backup-daemon-service>` on |k8s|.
+   This value is expressed as an integer followed by a unit of memory
+   in |jedec| notation.
 
    .. note::
 
@@ -540,8 +562,9 @@ Optional |onprem| Resource Settings
    *Type*: string
 
    Maximum memory capacity for the |k8s-node| being created to host
-   the :ref:`backup-daemon`. If omitted, this value is set to
-   :opsmgrkube:`spec.backup.statefulSet.spec.template.spec.containers.resources.requests.memory`.
+   the :opsmgr:`backup daemon service
+   </current/core/system-overview/#backup-daemon-service>`. If omitted,
+   this value is set to :opsmgrkube:`spec.backup.statefulSet.spec.template.spec.containers.resources.requests.memory`.
 
    The |k8s-op-short| calculates and sets parameters for Java heap size
    based on the container's memory.
@@ -596,7 +619,7 @@ Optional |onprem| Resource Settings
    .. note:: 
 
       If you deploy |onprem| 4.2, you must specify a MongoDB version
-      earlier than than 4.0 in the :ref:`resource definition
+      earlier than 4.0 in the :ref:`resource definition
       <k8s-specification>` for the database that stores the metadata for
       the |s3| snapshot store.
 
@@ -633,11 +656,11 @@ Optional |onprem| Resource Settings
    *Required if you enable Backup using an S3 store.*
 
    Name of the secret that contains the ``accessKey`` and
-   ``secretKey`` fields. The :ref:`backup-daemon` uses the values
-   of these fields as credentials to access your
-   |aws| |s3| or |s3|-compatible bucket. The |s3|
-   snapshot store can't be configured if the secret is missimg either
-   key.
+   ``secretKey`` fields. The :opsmgr:`backup daemon service
+   </current/core/system-overview/#backup-daemon-service>` uses
+   the values of these fields as credentials to access your
+   |aws| |s3| or |s3|-compatible bucket. The |s3| snapshot store
+   can't be configured if the secret is missing either key.
 
 .. opsmgrkube:: spec.backup.s3Stores.pathStyleAccessEnabled
 
@@ -884,7 +907,7 @@ Optional |onprem| Resource Settings
    To review which fields you can add to
    :opsmgrkube:`spec.statefulSet.spec`, see the
    :k8sdocs:`Kubernetes documentation
-   </reference/generated/kubernetes-api/v1.16/#statefulsetspec-v1-apps>`.
+   </reference/generated/kubernetes-api/v1.21/#statefulsetspec-v1-apps>`.
 
 .. opsmgrkube:: spec.statefulSet.spec.template
 
@@ -909,7 +932,7 @@ Optional |onprem| Resource Settings
    To review which fields you can add to
    :opsmgrkube:`spec.statefulSet.spec.template.metadata`, see
    the :k8sdocs:`Kubernetes documentation
-   </reference/generated/kubernetes-api/v1.16/#objectmeta-v1-meta>`.
+   </reference/generated/kubernetes-api/v1.21/#objectmeta-v1-meta>`.
 
 .. opsmgrkube:: spec.statefulSet.spec.template.spec
 
@@ -921,7 +944,7 @@ Optional |onprem| Resource Settings
    To review the complete list of fields you can add to
    :opsmgrkube:`spec.statefulSet.spec.template.spec`, see the
    :k8sdocs:`Kubernetes documentation
-   </reference/generated/kubernetes-api/v1.16/#podspec-v1-core>`.
+   </reference/generated/kubernetes-api/v1.21/#podspec-v1-core>`.
 
    The following example ``spec.statefulSet.spec.template.spec`` defines
    minimum and maximum CPU and memory capacity for one |onprem|

source/tutorial/create-operator-credentials.txt

@@ -49,7 +49,7 @@ To create credentials for the |k8s-op-short|, you must:
 
 #. Add the |ipaddr| or |cidr| block of any hosts that serve the
    |k8s-op-short| to the
-   :ref:`API Whitelist <configure-access-to-whitelisted-ops>`.
+   :opsmgr:`API Whitelist </tutorial/configure-public-api-access/>`.
 
 .. _create-k8s-secret-procedure: