(DOCSP-38872) Adds FAQs. (#1747)

* (DOCSP-38872) Adds FAQs.

* Revises per copy review.

Author: erabil-mdb

source/faq.txt

@@ -34,16 +34,58 @@ requirements for MongoDB Servers. The |k8s-op-short| also facilitates
 configuration of MongoDB Server features, such as database backups, 
 through interaction with |cloud| or |onprem|.
 
-Why should I run MongoDB Server and MongoDB Enterprise Advanced in |k8s|?
-------------------------------------------------------------------------------------
+.. _faq-k8s-advanced:
 
-When you deploy MongoDB Server or MongoDB Enterprise Advanced in |k8s| 
-through the |k8s-op-full|, your deployments can benefit from the 
-resilience and simple orchestration that |k8s| provides.
+Why run MongoDB Enterprise Advanced on |k8s|?
+--------------------------------------------------
 
-The only supported way to deploy MongoDB Enterprise Advanced in |k8s| is
-through the |k8s-op-full|. The |k8s-op-full| simplifies your daily workflows
-and makes it easier for MongoDB technical support staff to assist you when needed.
+Running MongoDB on |k8s| simplifies the setup and management of self-hosting MongoDB. 
+
+The |k8s-op-short| works with MongoDB and |mms| to automate configuration using 
+custom resource files that you create to define your setup. This allows you to 
+manage the configuration using whatever tools you already have for managing 
+applications in |k8s|, including tools that enable a GitOps workflow where 
+configuration is managed in a Git repository. The high level of automation and 
+abstraction from complexity makes |k8s| and the |k8s-op-short| especially well 
+suited to running MongoDB as a service, either for internal users or external customers.
+
+|k8s| allows MongoDB to take advantage of the scalability and automated resilience 
+that |k8s| offers, like the automated replacement of a lost Pod making up 
+a replica set or sharded cluster. This allows MongoDB to be highly scalable and 
+resilient when running in |k8s|.
+
+.. _faq-k8s-scalability:
+
+How scalable is MongoDB in |k8s|?
+--------------------------------------
+
+MongoDB within |k8s| is as scalable as MongoDB on bare metal or VMs. For many 
+customers, scalability is easier to achieve within |k8s|. The |k8s-op-short| and |k8s| 
+work seamlessly together to enable easy horizontal scaling, including the ability 
+to span MongoDB deployments across multiple |k8s| clusters for multi-cluster and 
+multi-site resilience. 
+
+Vertical scaling is as easy as changing the resources for a deployment in the 
+custom resource that defines it.
+
+All of this allows MongoDB to scale to meet any demands.
+
+.. _faq-k8s-downsides:
+
+Are there any downsides to running MongoDB within |k8s|?
+-------------------------------------------------------------
+
+There are no downsides from a technical perspective. MongoDB within |k8s| is as 
+performant and scalable as MongoDB running on any hardware or infrastructure. 
+
+But, as with any infrastructure, there is an inherent requirement for customers 
+to have familiarity and expertise with the technology, in this case |k8s|. 
+While the |k8s-op-short| simplifies and automates the setup of MongoDB within |k8s|, 
+there is still a dependency on the underlying resources and capabilities that are 
+part of the |k8s| cluster, things like stateful storage, networking, security, 
+and compute. This means that customers still need to ensure that those 
+services and resources are available and configured correctly to support MongoDB, 
+much as this would be needed if running on bare metal or virtual machines.
 
 Which |k8s| platforms are supported for MongoDB Server deployments?
 --------------------------------------------------------------------------------

source/index.txt

@@ -44,6 +44,11 @@ You can then deploy MongoDB databases as you deploy them now after the
 cluster is created. You can use the |com| console to run MongoDB at
 optimal performance.
 
+.. seealso::
+
+   - :ref:`faq-k8s-advanced`
+   - :ref:`k8s-faq`
+
 .. toctree::
    :titlesonly:
    :hidden: