@@ -17,15 +17,6 @@ The |k8s-op-full| uses a |k8s| |k8s-configmap| to link to a single, unique
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.
19
19
20
- .. note::
21
-
22
- As each |k8s-op-full| deployment requires a one to one pairing with
23
- a unique |onprem| :opsmgr:`Project </tutorial/manage-projects>`,
24
- you can either create a distinct ConfigMap for each |k8s-op-full| instance
25
- you deploy, or you can reuse the same ConfigMap for any number of deployments
26
- by omitting the ``data.projectName`` from your ConfigMap, so that
27
- project names will be randomly generated as required.
28
-
29
20
To create a |k8s-op-short| ConfigMap, you can edit a few lines of the
30
21
:ref:`example ConfigMap <example-k8s-configmap>` |yaml| file and apply
31
22
the ConfigMap. To view a full example, see the :github:`project.yaml
@@ -45,6 +36,15 @@ applies because |onprem| supports only one authentication method for
45
36
database user access per project. To learn more, see
46
37
:ref:`k8s-deploy-mdb-resources`.
47
38
39
+ .. note::
40
+
41
+ Each |k8s-op-full| deployment requires a 1:1 pairing with
42
+ a unique |onprem| :opsmgr:`Project </tutorial/manage-projects>`.
43
+ You can either create a distinct ConfigMap for each |k8s-op-full| instance
44
+ you deploy, or you can reuse the same ConfigMap for any number of deployments
45
+ by omitting the ``data.projectName`` from your ConfigMap, so that
46
+ project names align with deployed resource names.
47
+
48
48
.. include:: /includes/admonitions/note-k8s-supported-in-om4.rst
49
49
50
50
Prerequisites
0 commit comments