Skip to content

Commit 02a0d39

Browse files
author
alisovenko
committed
390b89833889c1af537495c739a587d6aa2c119a: update public repo contents
1 parent e0bcfdc commit 02a0d39

File tree

1 file changed

+10
-1
lines changed

1 file changed

+10
-1
lines changed

README.md

Lines changed: 10 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -32,6 +32,16 @@ This Operator requires Ops Manager or Cloud Manager. In this document, when we r
3232

3333
## Installation ##
3434

35+
### Create Kubernetes Namespace ###
36+
37+
The Mongodb Enterprise Operator is installed, by default, into the `mongodb` Namespace, but this Namespace is not created automatically. To create this Namespace you should execute:
38+
39+
kubectl create namespace mongodb
40+
41+
If you plan on using any other Namespace, please make sure you update the yaml files' `metadata.namespace` attribute to
42+
point to your preferred Namespace. If using `helm` you need to override the `namespace` attribute with `--set namespace=<..>`
43+
during helm installation
44+
3545
### Create CustomResourceDefinitions
3646

3747
The `CustomResourceDefinition` (or `crds`) should be installed before installing the operator into your Kubernetes cluster. To do this, make sure you have logged into your Kubernetes cluster and that you can perform Cluster level operations:
@@ -59,7 +69,6 @@ If you have an Helm installation in your Kubernetes cluster, you can run:
5969

6070

6171

62-
6372
## Adding Ops Manager Credentials ##
6473

6574
For the Operator to work, you will need the following information:

0 commit comments

Comments
 (0)