(DOCSP-11892): Adjust Kubernetes Docs with known scaling configuration issue

Author: jwilliams-mongo

source/release-notes.txt

@@ -63,6 +63,9 @@ Known Issues
 ~~~~~~~~~~~~
 
 - |onprem| cannot monitor Application Databases secured using |tls|.
+-  For MongoDB 4.4 deployments, you can increase or decrease the number
+   of members in a replica set or a sharded cluster by only one member
+   at a time.
 
 .. _ent-op-1.6.1:
 

source/tutorial/scale-resources.txt

@@ -53,25 +53,44 @@ Scale a Sharded Cluster
 Considerations
 --------------
 
-The |k8s-op-short| does not support modifying deployment types.
-For example, you cannot convert a standalone deployment to a
-replica set. To modify the type of a deployment,
-we recommend the following procedure:
+-  For MongoDB 4.4 deployments, you can increase or decrease the
+   number of members in a replica set or a sharded cluster by only one
+   member at a time.
 
-1. Create the new deployment with the desired configuration.
+   .. example::
 
-#. :opsmgr:`Back up the data </tutorial/nav/backup-deployments/>` from
-   your current deployment.
+      To scale a replica set from three members to five members, you
+      must:
 
-#. :opsmgr:`Restore the data
-   </tutorial/nav/backup-restore-deployments/>` from your current
-   deployment to the new deployment.
+      1. Change the value of the :setting:`spec.members` setting from
+         ``3`` to ``4``.
 
-#. Test your application connections to the new deployment as needed.
+      #. Reapply the configuration to |k8s|.
 
-#. Once you have verified that the new deployment contains the
-   required data and can be reached by your application(s), bring
-   down the old deployment.
+      #. Change the value of the :setting:`spec.members` setting from
+         ``4`` to ``5``.
+
+      #. Reapply the configuration to |k8s|.
+
+- The |k8s-op-short| does not support modifying deployment types.
+  For example, you cannot convert a standalone deployment to a
+  replica set. To modify the type of a deployment,
+  we recommend the following procedure:
+
+  1. Create the new deployment with the desired configuration.
+
+  #. :opsmgr:`Back up the data </tutorial/nav/backup-deployments/>` from
+     your current deployment.
+
+  #. :opsmgr:`Restore the data
+     </tutorial/nav/backup-restore-deployments/>` from your current
+     deployment to the new deployment.
+
+  #. Test your application connections to the new deployment as needed.
+
+  #. Once you have verified that the new deployment contains the
+     required data and can be reached by your application(s), bring
+     down the old deployment.
 
 Examples
 --------
@@ -99,6 +118,12 @@ want to scale:
       1. Adjust the :setting:`spec.members` setting to the desired
          number of members:
 
+         .. important::
+
+            For MongoDB 4.4 deployments, you can increase or decrease
+            the number of members in a replica set by only one member at
+            a time.
+
          .. literalinclude:: /includes/code-examples/yaml-files/example-replica-set.yaml
             :language: yaml
             :start-after: START-scaled-replset
@@ -129,6 +154,12 @@ want to scale:
 
       1. Adjust the following settings to the desired values:
 
+         .. important::
+
+            For MongoDB 4.4 deployments, you can increase or decrease
+            the number of members in a sharded cluster by only one
+            member at a time. 
+
          - :setting:`spec.shardCount`
          - :setting:`spec.mongodsPerShardCount`
          - :setting:`spec.mongosCount`