@@ -12,7 +12,7 @@ Create One Project using a ConfigMap
12
12
:depth: 1
13
13
:class: singlecol
14
14
15
- The |k8s-op-full| uses a |k8s| |k8s-configmap| to link your
15
+ The |k8s-op-full| uses a |k8s| |k8s-configmap| to link to a single and unique
16
16
|onprem| :opsmgr:`Project </tutorial/manage-projects>`. If the
17
17
referenced project doesn't exist, the |k8s-op-short| creates it
18
18
according to the ``projectName`` that you provide in the ConfigMap.
@@ -31,10 +31,19 @@ which you can then apply to your Kubernetes environment.
31
31
Considerations
32
32
--------------
33
33
34
- You can deploy only one MongoDB resource per project. This limit
35
- applies because |onprem| supports only one authentication method for
36
- database user access per project. To learn more, see
37
- :ref:`k8s-deploy-mdb-resources`.
34
+ 1. You can deploy only one MongoDB resource per project. This limit
35
+ applies because |onprem| supports only one authentication method for
36
+ database user access per project. To learn more, see
37
+ :ref:`k8s-deploy-mdb-resources`.
38
+
39
+ 2. You must pair a |k8s-op-full| deployment to a unique
40
+ |onprem| :opsmgr:`Project </tutorial/manage-projects>`.
41
+ You can either create a distinct ConfigMap for each |k8s-op-full| instance
42
+ you deploy, or you can reuse the same ConfigMap for any number of deployments
43
+ by omitting the ``data.projectName`` from your ConfigMap, so that
44
+ project names align with deployed resource names. Where a project name is
45
+ provided in the config map, if that project does not
46
+ exist yet it will be created.
38
47
39
48
.. include:: /includes/admonitions/note-k8s-supported-in-om4.rst
40
49
0 commit comments