Skip to content

Commit b5d55cb

Browse files
lmkerbey-mdbjwilliams-mongo
authored andcommitted
(DOCSP-25895) Create MEKO FAQ (#1192)
* (DOCSP-25895) First draft. * (DOCSP-25895) Formatting fix. * (DOCSP-25895) Formatting fix. * (DOCSP-25895) Add to ToC * (DOCSP-25895) * (DOCSP-25895) Copy review. * (DOCSP-25895) Copy review * (DOCSP-25895) * (DOCSP-25895) Copy review.
1 parent c5b2b7b commit b5d55cb

File tree

3 files changed

+84
-0
lines changed

3 files changed

+84
-0
lines changed

source/faq.txt

Lines changed: 81 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,81 @@
1+
.. _k8s-faq:
2+
3+
==========================
4+
Frequently Asked Questions
5+
==========================
6+
7+
.. default-domain:: mongodb
8+
9+
.. contents:: On this page
10+
:local:
11+
:backlinks: none
12+
:depth: 1
13+
:class: singlecol
14+
15+
16+
.. _faq-k8s-run-mongo:
17+
18+
What is an Operator?
19+
--------------------
20+
21+
An operator is a standard mechanism that extends the control plane of
22+
|k8s| to managing custom |k8s| resources. Because each operator is
23+
built for its own Custom Resources (CRs), it can contain logic that
24+
addresses the type of service that the operator is built for. For the
25+
|k8s-op-short|, the operator includes the logic for the deployment of
26+
MongoDB Server and Ops Manager instances.
27+
28+
Each CR used by the |k8s-op-short| represents an element of a MongoDB
29+
Server deployment in |k8s|, and has options for customizing that part
30+
of the deployment. Once you configure these objects in the |k8s|
31+
deployment, the operator builds native |k8s| objects, such as Stateful
32+
Sets that are necessary to create Pods according to your specified
33+
requirements for MongoDB Servers. The operator also facilitates
34+
configuration of MongoDB Server features, such as database backups,
35+
through interaction with |cloud| or |onprem|.
36+
37+
Why should I run MongoDB Server and MongoDB Enterprise Advanced in |k8s|?
38+
--------------------------------------------------------------------------
39+
40+
When you deploy MongoDB Server or MongoDB Enterprise Advanced in |k8s|
41+
through the |k8s-op-full|, your deployments can benefit from the
42+
resilience and simple orchestration that |k8s| provides.
43+
44+
The only supported way to deploy MongoDB Enterprise Advanced in |k8s| is
45+
through the |k8s-op-full|. The |k8s-op-full| simplifies your daily
46+
workflows and makes it easier for MongoDB technical support staff to
47+
assist you when needed.
48+
49+
Which |k8s| platforms are supported for MongoDB Server deployments?
50+
-------------------------------------------------------------------------
51+
52+
MongoDB Server supports any platform that builds upon native |k8s|
53+
without changing the default logic or behavior. In practice, this means
54+
that MongoDB Server supports any |k8s| platform
55+
`certified by the Cloud Native Computing Foundation <https://www.cncf.io/certification/software-conformance/>`_.
56+
To learn more, see
57+
:ref:`MongoDB Kubernetes Operator Compatibility <k8s-compatibility>`.
58+
59+
How many deployments can |k8s-op-full| support?
60+
-----------------------------------------------
61+
62+
|k8s-op-short| can support up to 50 deployments. However, changes made
63+
to large numbers of deployments at the same time result in long
64+
reconciliation times. To avoid prolonged reconciliation times, limit a
65+
given |k8s-op-short| instance to 20 deployments. To learn more,
66+
see the :ref:`production notes <deploy_recommended-number-sets>`.
67+
68+
Should I run MongoDB Server in |k8s| in the same cluster as the application using it?
69+
--------------------------------------------------------------------------------------
70+
71+
To help minimize latency, consider colocating your database and
72+
applications on the same |k8s| cluster if your deployment architecture
73+
allows this.
74+
75+
Can I deploy MongoDB Server across multiple |k8s| clusters?
76+
-----------------------------------------------------------
77+
78+
This feature is available in Beta releases, as described in
79+
:ref:`Deploy MongoDB Resources on Multiple Kubernetes Clusters <multi-cluster>`.
80+
To learn more,
81+
`contact Support <https://cloud.mongodb.com/links/support>`_.

source/index.txt

Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -57,6 +57,7 @@ optimal performance.
5757
Deploy MongoDB Resources on Multiple Kubernetes Clusters (Beta) </multi-cluster>
5858
/tutorial/modify-resource-image
5959
/reference
60+
FAQ </faq.txt>
6061
Release Notes </release-notes>
6162
Production Notes </reference/production-notes>
6263
/reference/troubleshooting

source/reference/production-notes.txt

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -124,6 +124,8 @@ GitHub directory:
124124
* - :github:`ops_manager_wizardless </10gen/mongodb-enterprise-kubernetes/tree/master/opa_examples/ops_manager_wizardless>`
125125
- Allows installing |onprem| in a non-interactive mode.
126126

127+
.. _deploy_recommended-number-sets:
128+
127129
Deploy the Recommended Number of MongoDB Replica Sets
128130
-----------------------------------------------------
129131

0 commit comments

Comments
 (0)