Skip to content

Commit ff32852

Browse files
DOCSP-33529 -- edit
1 parent 7fc4017 commit ff32852

File tree

2 files changed

+10
-10
lines changed

2 files changed

+10
-10
lines changed

source/includes/steps-create-k8s-configmap.yaml

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -20,7 +20,7 @@ content: |
2020
name: my-project
2121
namespace: mongodb
2222
data:
23-
projectName: myProjectName # optional; omit to generate a random project name
23+
projectName: myProjectName # optional; omit to create a project with the resource name
2424
orgId: 5b890e0feacf0b76ff3e7183 # this is a required parameter
2525
baseUrl: https://ops.example.com:8443
2626

source/tutorial/create-project-using-configmap.txt

Lines changed: 9 additions & 9 deletions
Original file line numberDiff line numberDiff line change
@@ -17,15 +17,6 @@ The |k8s-op-full| uses a |k8s| |k8s-configmap| to link to a single, unique
1717
referenced project doesn't exist, the |k8s-op-short| creates it
1818
according to the ``projectName`` that you provide in the ConfigMap.
1919

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-
2920
To create a |k8s-op-short| ConfigMap, you can edit a few lines of the
3021
:ref:`example ConfigMap <example-k8s-configmap>` |yaml| file and apply
3122
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
4536
database user access per project. To learn more, see
4637
:ref:`k8s-deploy-mdb-resources`.
4738

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+
4848
.. include:: /includes/admonitions/note-k8s-supported-in-om4.rst
4949

5050
Prerequisites

0 commit comments

Comments
 (0)