|
2 | 2 |
|
3 | 3 | Welcome to the MongoDB Enterprise Kubernetes Operator. The Operator enables easy deploys of MongoDB into Kubernetes clusters, using our management, monitoring and backup platforms, Ops Manager and Cloud Manager. By installing this integration, you will be able to deploy MongoDB instances with a single simple command. |
4 | 4 |
|
| 5 | +Also the Operator allows to deploy Ops Manager into Kubernetes. Note, that currently this feature is **alpha**. See more information below. |
| 6 | + |
5 | 7 | You can discuss this integration in our [Slack](https://community-slack.mongodb.com) - join the [#enterprise-kubernetes](https://mongo-db.slack.com/messages/CB323LCG5/) channel. |
6 | 8 |
|
7 | 9 | ## Documentation ## |
@@ -77,7 +79,11 @@ You can customize installation by simple overriding of helm variables, for examp |
77 | 79 |
|
78 | 80 | Check the end of the page for instructions on how to remove the Operator. |
79 | 81 |
|
80 | | -## Adding Ops Manager Credentials ## |
| 82 | +## MongoDB object ## |
| 83 | + |
| 84 | +*This section describes how to create the MongoDB resource. Follow the next section on how to work with Ops Manager resource.* |
| 85 | + |
| 86 | +### Adding Ops Manager Credentials ### |
81 | 87 |
|
82 | 88 | For the Operator to work, you will need the following information: |
83 | 89 |
|
@@ -131,7 +137,34 @@ If you have a correctly created Project with the name `my-project` and Credentia |
131 | 137 |
|
132 | 138 | kubectl apply -f samples/minimal/replicaset.yaml |
133 | 139 |
|
134 | | -### Correct order of Operator/Namespace removal |
| 140 | +## Ops Manager object (alpha) ## |
| 141 | + |
| 142 | +This section describes how to create the Ops Manager object in Kubernetes. |
| 143 | + |
| 144 | +*Disclaimer: this is an early release of Ops Manager - so it's not recommended to use it in production * |
| 145 | + |
| 146 | +### Create Admin Credentials Secret ### |
| 147 | + |
| 148 | +Before creating the Ops Manager object you need to prepare the information about the admin user which will be created automatically. You can use the following command to do it: |
| 149 | + |
| 150 | +```bash |
| 151 | +$ kubectl create secret generic ops-manager-admin-secret --from-literal=Username="jane.doe@example.com" --from-literal=Password="Passw0rd." --from-literal=FirstName="Jane" --from-literal=LastName="Doe" -n <namespace> |
| 152 | +``` |
| 153 | + |
| 154 | +Note, that the secret is needed only during the initialization of the Ops Manager object - you can remove it or clean the password field after the Ops Manager object was created |
| 155 | + |
| 156 | +### Create Ops Manager object ### |
| 157 | + |
| 158 | +Use the file `samples/ops-manager/ops-manager.yaml`. Edit the fields and create the object in Kubernetes: |
| 159 | + |
| 160 | +```bash |
| 161 | +$ kubectl apply -f samples/ops-manager/ops-manager.yaml |
| 162 | +``` |
| 163 | + |
| 164 | +Note, that it takes up to 10 minutes to initialize the Application Database and start Ops Manager. |
| 165 | + |
| 166 | + |
| 167 | +## Deleting the Operator ## |
135 | 168 |
|
136 | 169 | It's important to keep correct order or removal operations. The simple rule is: **never remove Operator before mongodb resources**! |
137 | 170 | The reason is that the Operator cleans state in Ops Manager on deletion of the MongoDB resource in Kubernetes. |
|
0 commit comments