(DOCSP-37101) Atlas defaults to 7.0 (#30)

* (DOCSP-37101) Atlas defaults to 7.0

* Add a PR template

* edits

* Edits, formatting only, no content changes

Author: JuliaMongo

source/atlasdeployment-custom-resource.txt

@@ -12,26 +12,26 @@
    :depth: 2
    :class: singlecol
 
-The ``AtlasDeployment`` custom resource configures your MongoDB 
-{+cluster+} or {+serverless-instance+} in |service|. When you create
-the ``AtlasDeployment`` custom resource, |ak8so| tries to create or 
-update a {+cluster+} or {+serverless-instance+} in |service|.
+The ``AtlasDeployment`` custom resource configures your MongoDB {+cluster+}
+or {+serverless-instance+} in |service|. When you create the ``AtlasDeployment``
+custom resource, |ak8so| tries to create or update a {+cluster+} or
+{+serverless-instance+} in |service|.
 
 .. important:: Action Required for Breaking Changes with |ak8so| 2.0
 
    * With |ak8so| 2.0, ``deploymentSpec`` replaces ``advancedDeploymentSpec`` in 
      the ``AtlasDeployment`` custom resource. You must update your ``AtlasDeployment`` 
      custom resource as follows:
 
-     * If you use ``advancedDeploymentSpec``, rename to ``deploymentSpec``. 
+     * If you use ``advancedDeploymentSpec``, rename it to ``deploymentSpec``. 
        You don't need to change any formatting.
 
      * If you used ``deploymentSpec`` prior to |ak8so| 2.0, rewrite your 
        ``AtlasDeployment`` custom resource to match the formatting used in 
        :ref:`the examples <atlasdeployment-examples>`.
 
    * |ak8so| uses :ref:`custom resource <custom-resources>` configuration
-     files to manage your |service| configuration, but as of |ak8so| 2.0,
+     files to manage your |service| configuration. As of |ak8so| 2.0,
      custom resources you delete in |k8s| are no longer deleted in 
      |service|. Instead, |ak8so| simply stops managing those resources.  
      For example, if you delete an :ref:`atlasproject-custom-resource`
@@ -40,17 +40,15 @@ update a {+cluster+} or {+serverless-instance+} in |service|.
      including how to :ref:`revert this behavior <revert-deletion-protection>` to 
      the default used prior to |ak8so| 2.0, see :ref:`deletion-protection`.
 
-|ak8so| does one of the following actions depending on the 
-values you specify in the ``AtlasDeployment`` custom resource:
+|ak8so| does one of the following actions depending on the values you
+specify in the ``AtlasDeployment`` custom resource:
 
-- If you specify values for fields under ``spec.deploymentSpec``, 
-  |ak8so| uses the |service| :oas-atlas-tag:`Clusters API Resource 
-  </Clusters>` to create a new {+cluster+} or
-  update an existing {+cluster+}.
-- If you specify values for fields under ``spec.serverlessSpec``,
-  |ak8so| uses the |service| :oas-atlas-tag:`Serverless Instance API 
-  Resource </Serverless-Instances>` to create a new 
-  {+serverless-instance+} or update an existing {+serverless-instance+}.
+- If you specify values for fields under ``spec.deploymentSpec``, |ak8so|
+  uses the |service| :oas-atlas-tag:`Clusters API Resource </Clusters>`
+  to create a new {+cluster+} or update an existing {+cluster+}.
+- If you specify values for fields under ``spec.serverlessSpec``, |ak8so|
+  uses the |service| :oas-atlas-tag:`Serverless Instance API Resource </Serverless-Instances>`
+  to create a new {+serverless-instance+} or update an existing {+serverless-instance+}.
 
 Creating or updating a {+cluster+} or {+serverless-instance+} can take
 up to 10 minutes. |ak8so| monitors the update process.
@@ -74,8 +72,8 @@ provisioning:
        reason: ClusterCreating 
        message: Cluster is provisioning
 
-The ``ClusterReady`` status will change to ``True`` when the 
-{+cluster+} or {+serverless-instance+} is ready.
+The ``ClusterReady`` status will change to ``True`` when the {+cluster+}
+or {+serverless-instance+} is ready.
 
 .. _atlasdeployment-examples:
 
@@ -85,7 +83,7 @@ Examples
 Status Example
 ~~~~~~~~~~~~~~
 
-The following example shows the ``AtlasDeployment`` resource with a  
+The following example shows the ``AtlasDeployment`` resource with a
 ``ClusterReady`` status of ``True``:
 
 .. code-block::
@@ -134,7 +132,7 @@ The following example shows the ``AtlasDeployment`` resource with a
 
 Configuration Example
 ~~~~~~~~~~~~~~~~~~~~~
-     
+
 The following example shows an ``AtlasDeployment`` custom resource 
 specification configured for autoscaling multi-region {+clusters+}:
 
@@ -187,8 +185,8 @@ specification configured for autoscaling multi-region {+clusters+}:
 Additional Options Example
 ~~~~~~~~~~~~~~~~~~~~~~~~~~
 
-The following example shows an ``AtlasDeployment`` custom resource 
-specification configured with some of the :oas-atlas-tag:`additional options 
+The following example shows an ``AtlasDeployment`` custom resource
+specification configured with some of the :oas-atlas-tag:`additional options
 </Clusters>`.
 
 .. code-block::
@@ -219,7 +217,7 @@ specification configured with some of the :oas-atlas-tag:`additional options
 {+Serverless-Instance+} Example
 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
 
-The following example shows an ``AtlasDeployment`` custom resource 
+The following example shows an ``AtlasDeployment`` custom resource
 specification configured for a {+serverless-instance+}:
 
 .. code-block::
@@ -246,10 +244,10 @@ specification configured for a {+serverless-instance+}:
 .. _ak8so-advanced-clusters:
 
 Multi-Region {+Cluster+} Example
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
 
-{+Clusters+} can span regions and cloud service providers. To 
-learn more, see :ref:`create-new-cluster-considerations`.
+{+Clusters+} can span regions and cloud service providers. To learn more,
+see :ref:`create-new-cluster-considerations`.
 
 .. note::
 
@@ -288,10 +286,9 @@ resource specification configured for multi-region {+clusters+}:
 
 Multiple Cloud Service Providers Example
 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-     
-The following example shows an ``AtlasDeployment`` custom 
-resource specification configured to span multiple cloud service 
-providers:
+
+The following example shows an ``AtlasDeployment`` custom resource
+specification configured to span multiple cloud service providers:
 
 .. code-block::
 
@@ -336,24 +333,26 @@ providers:
 Parameters
 ----------
 
-This section describes some of the key ``AtlasDeployment`` custom 
-resource parameters available. For a full list of available parameters
-for {+clusters+}, see the |service| :oas-atlas-op:`{+Clusters+} API 
-</createCluster>`. For a full list of available parameters for 
-{+serverless-instances+}, see the |service| 
-:oas-atlas-tag:`{+Serverless-Instances+} API </Serverless-Instances>`.
+This section describes some of the key ``AtlasDeployment`` custom resource
+parameters available.
+
+- For a full list of available parameters for {+clusters+},
+  see the |service| :oas-atlas-op:`{+Clusters+} API </createCluster>`.
 
-Refer to these descriptions, the available examples, and the |api| 
-documentation to customize your specifications.
+- For a full list of available parameters for {+serverless-instances+},
+  see the |service| :oas-atlas-tag:`{+Serverless-Instances+} API </Serverless-Instances>`.
+
+To customize your specifications, Refer to these descriptions, the available
+examples, and the |api| documentation.
 
 .. setting:: spec.backupRef
 
    *Type*: object
 
    *Optional*
 
-   List that contains the details for the 
-   :ref:`atlasbackupschedule-custom-resource` that you want to apply. You can specify one backup schedule per {+cluster+}.
+   List that contains the details for the :ref:`atlasbackupschedule-custom-resource`
+   that you want to apply. You can specify one backup schedule per {+cluster+}.
 
 .. setting:: spec.backupRef.name
 
@@ -362,13 +361,12 @@ documentation to customize your specifications.
    *Optional*
 
    ``metadata.name`` value within the 
-   :ref:`atlasbackupschedule-custom-resource` for the backup schedule
-   that you want to apply. You can specify only one backup schedule per 
-   {+cluster+}, but you can use the same backup schedule for multiple 
-   {+clusters+}.
+   :ref:`atlasbackupschedule-custom-resource` for the backup schedule that
+   you want to apply. You can specify only one backup schedule per {+cluster+},
+   but you can use the same backup schedule for multiple {+clusters+}.
 
-   If you don't specify this parameter, |service| doesn't apply your
-   backup configuration to this {+cluster+}.
+   If you omit this parameter, |service| doesn't apply your backup
+   configuration to this {+cluster+}.
 
 .. setting:: spec.backupRef.namespace
 
@@ -392,8 +390,8 @@ documentation to customize your specifications.
 
    .. important::
 
-      You must specify ``spec.deploymentSpec`` 
-      or ``spec.serverlessSpec`` in your configuration.
+      You must specify ``spec.deploymentSpec`` or ``spec.serverlessSpec``
+      in your configuration.
 
 .. setting:: spec.deploymentSpec.clusterType
 
@@ -419,8 +417,7 @@ documentation to customize your specifications.
           :atlas:`Global {+Clusters+} </global-clusters>`.
         - Required
 
-      * - You are deploying non-Global replica sets and sharded
-          {+clusters+}.
+      * - You are deploying non-Global replica sets and sharded {+clusters+}.
         - Optional
 
    |service| accepts:
@@ -456,33 +453,31 @@ documentation to customize your specifications.
 
    *Optional*
 
-   Capacity, in gigabytes, that indicates the host's root volume.
-   Increase this number to add capacity, up to a maximum possible value 
-   of ``4096`` (4 TB). You must specify a positive number for 
-   this value.
+   Capacity, in gigabytes, that indicates the host's root volume. Increase
+   this number to add capacity, up to a maximum possible value of
+   ``4096`` (4 TB). You must specify a positive number for this value.
 
    You can't set this value for |nvme-clusters|.
 
    .. note::
 
-      If you enable autoscaling for ``diskGB`` in any region, you 
-      can't edit this option. To learn more, see 
-      :setting:`spec.deploymentSpec.replicationSpecs.regionConfigs.autoScaling.diskGB.enabled`.
+      If you enable autoscaling for ``diskGB`` in any region, you can't edit
+      this option. To learn more, see :setting:`spec.deploymentSpec.replicationSpecs.regionConfigs.autoScaling.diskGB.enabled`.
 
-   The minimum disk size for {+dedicated-clusters+} is 10 GB for |aws|
-   and |gcp|. If you specify this setting with a lower disk size,
-   |service| defaults to the minimum disk size value.
+   The minimum disk size for {+dedicated-clusters+} is 10 GB for |aws| and
+   |gcp|. If you specify this setting with a lower disk size, |service|
+   defaults to the minimum disk size value.
 
-   If your {+database-deployment+} includes |azure| nodes, this value 
-   must correspond to an existing |azure| disk type (8, 16, 32, 64, 
-   128, 256, 512, 1024, 2048, or 4096).
+   If your {+database-deployment+} includes |azure| nodes, this value must
+   correspond to an existing |azure| disk type (8, 16, 32, 64, 128, 256,
+   512, 1024, 2048, or 4096).
 
-   |service| calculates storage charges differently depending on
-   whether you choose the default value or a custom value.
+   |service| calculates storage charges differently depending on whether
+   you choose the default value or a custom value.
 
    .. include:: /includes/cluster-settings/extended-storage-limit.rst
 
-   If your {+database-deployment+} spans cloud service providers, this 
+   If your {+database-deployment+} spans cloud service providers, this
    value defaults to the minimum default of the providers involved.
 
    To learn more, see :ref:`storage-capacity`.
@@ -493,11 +488,9 @@ documentation to customize your specifications.
 
    *Optional*
 
-   Cloud service provider that manages the customer key for this 
-   {+cluster+}. You must set this value to enable encryption at rest
-   using customer-managed keys for this {+cluster+}, which provides an
-   additional layer of encryption.
-   
+   Cloud service provider that manages the customer key for this {+cluster+}.
+   You must set this value to enable encryption at rest using customer-managed
+   keys for this {+cluster+}, which provides an additional layer of encryption.
    To learn more, see :ref:`ak8so-ear`.
 
    |service| accepts the following values:
@@ -572,17 +565,17 @@ documentation to customize your specifications.
 
       * - You omit this parameter and you omit the 
           :setting:`spec.deploymentSpec.versionReleaseSystem` parameter.
-        - |service| deploys a {+cluster+} that runs MongoDB 6.0.
+        - |service| deploys a {+cluster+} that runs MongoDB 7.0.
 
       * - You omit this parameter and you set the
           :setting:`spec.deploymentSpec.versionReleaseSystem` parameter to 
           ``LTS``.
-        - |service| deploys a {+cluster+} that runs MongoDB 6.0.
+        - |service| deploys a {+cluster+} that runs MongoDB 7.0.
 
       * - You set the 
           :setting:`spec.deploymentSpec.providerSettings.instanceSizeName` 
           parameter to ``M0``, ``M2``, or ``M5``.
-        - You must deploy MongoDB 6.0.
+        - You must deploy MongoDB 7.0.
 
       * - You specify this parameter.
         - |service| always deploys the {+cluster+} with the latest 
@@ -599,24 +592,21 @@ documentation to customize your specifications.
 
    *Conditional*
 
-   Configuration that enables continuous cloud backup. To enable
-   continuous cloud backup, you must specify this setting with a value
-   of ``true``.
+   Configuration that enables continuous cloud backup. To enable continuous
+   cloud backup, you must specify ``true`` for this setting.
 
 .. setting:: spec.deploymentSpec.providerSettings
 
    *Type*: Object
 
    *Conditional*
 
-   Configuration that specifies the settings for the provisioned hosts 
-   on which MongoDB runs. The available options are specific to the 
-   cloud service provider. To learn more, see the :ref:`AWS 
-   <amazon-aws>`, :ref:`GCP <google-gcp>`, and :ref:`Azure 
-   <microsoft-azure>` {+cluster+} configuration options.
+   Configuration that specifies the settings for the provisioned hosts on
+   which MongoDB runs. The available options are specific to the cloud service
+   provider. To learn more, see the :ref:`AWS <amazon-aws>`, :ref:`GCP <google-gcp>`,
+   and :ref:`Azure <microsoft-azure>` {+cluster+} configuration options.
 
-   If you want to create or update a {+cluster+}, you must
-   specify this setting.
+   If you want to create or update a {+cluster+}, you must specify this setting.
 
 .. setting:: spec.deploymentSpec.providerSettings.providerName
 
@@ -643,11 +633,11 @@ documentation to customize your specifications.
 
    *Required*
 
-   |service| provides different {+cluster+} tiers, each with a default
-   storage capacity and RAM size. The {+cluster+} you select is
-   used for all the data-bearing servers in your {+cluster+}. To learn 
-   more, see the :ref:`AWS <amazon-aws>`, :ref:`GCP <google-gcp>`, and 
-   :ref:`Azure <microsoft-azure>` custom storage sizes.
+   |service| provides different {+cluster+} tiers, each with a default storage
+   capacity and RAM size. The {+cluster+} you select is used for all the
+   data-bearing servers in your {+cluster+}. To learn more, see the
+   :ref:`AWS <amazon-aws>`, :ref:`GCP <google-gcp>`, and :ref:`Azure <microsoft-azure>`
+   custom storage sizes.
 
    If you change the instance size name after you deploy your 
    {+cluster+}, |service| changes the {+database-deployment+} to the