A Helm Chart for installing and upgrading the MongoDB Enterprise Kubernetes Operator.
The installation of this Chart does not have prerequisites. However, in order to create a Mongo Database in your Kubernetes cluster, you'll need a Cloud Manager account or an Ops Manager installation.
You can install the MongoDB Enterprise Operator easily with:
helm install enterprise-operator mongodb/enterprise-operator
This will install CRD
s and the Enterprise Operator in the current namespace
(default
by default). You can pass a different namespace with:
helm install enterprise-operator mongodb/enterprise-operator --namespace mongodb [--create-namespace]
To install the Enterprise Operator in a namespace called mongodb
; with the
optional --create-namespace
Helm will create the Namespace if it does not exist.
The Enteprise Operator can run against an account of Cloud Manager or Ops Manager.
Please visit "Configure Kubernetes for Deploying MongoDB
Resource"
in order to create new Secret
s and ConfigMap
s with credentials for your
Cloud Manager project.
You will create a ConfigMap
with name my-project
, and a Secret
with name
my-credentials
.
The Enterprise Operator will be watching for resources of type
mongodb.mongodb.com
(among others); you can quickly install
a sample Mongo Database with:
kubectl apply -f https://raw.githubusercontent.com/mongodb/mongodb-enterprise-kubernetes/master/samples/mongodb/minimal/replica-set.yaml [--namespace mongodb]
- Note: Make sure you add the
--namespace
option when needed.
After a few minutes you will have a 3-member MongoDB Replica Set installed in your cluster, that you can check with:
$ kubectl get mdb
NAME PHASE VERSION
my-replica-set Running 4.4.0-ent
Please follow the Official MongoDB Enterprise Kubernetes Operator for additional deployment topologies and multitude of other MongoDB options.