You are looking at the documentation of a prior release. To read the documentation of the latest release, please
visit here.
New to KubeDB? Please start here.
Initialize MongoDB with Snapshot
This tutorial will show you how to use KubeDB to initialize a MongoDB database with an existing snapshot.
Before You Begin
At first, you need to have a Kubernetes cluster, and the kubectl command-line tool must be configured to communicate with your cluster. If you do not already have a cluster, you can create one by using Minikube.
Now, install KubeDB cli on your workstation and KubeDB operator in your cluster following the steps here.
This tutorial assumes that you have created a namespace
demoand a snapshotsnapshot-infant. Follow the steps here to create a database and take instant snapshot, if you have not done so already. If you have changed the name of either namespace or snapshot object, please modify the YAMLs used in this tutorial accordingly.
Note: The yaml files used in this tutorial are stored in docs/examples/mongodb folder in GitHub repository kubedb/cli.
Create MongoDB with Init-Snapshot
Below is the MongoDB object created in this tutorial.
apiVersion: kubedb.com/v1alpha1
kind: MongoDB
metadata:
name: mgo-init-snapshot
namespace: demo
spec:
version: "3.4-v1"
storage:
storageClassName: "standard"
accessModes:
- ReadWriteOnce
resources:
requests:
storage: 50Mi
init:
snapshotSource:
name: snapshot-infant
namespace: demo
$ kubedb create -f https://raw.githubusercontent.com/kubedb/cli/0.9.0-rc.0/docs/examples/mongodb/Initialization/demo-2.yaml
mongodb.kubedb.com/mgo-init-snapshot created
Here,
spec.init.snapshotSource.namerefers to a Snapshot object for a MongoDB database in the same namespaces as this newmgo-init-snapshotMongoDB object.
Now, wait several seconds. KubeDB operator will create a new StatefulSet. Then KubeDB operator launches a Kubernetes Job to initialize the new database using the data from snapshot-infant Snapshot.
$ kubedb get mg -n demo
NAME VERSION STATUS AGE
mgo-infant 3.4-v1 Running 4m
mgo-init-snapshot 3.4-v1 Initializing 53s
$ kubedb describe mg -n demo mgo-init-snapshot
Name: mgo-init-snapshot
Namespace: demo
CreationTimestamp: Tue, 25 Sep 2018 13:06:41 +0600
Labels: <none>
Annotations: kubedb.com/initialized=
Replicas: 1 total
Status: Running
StorageType: Durable
Volume:
StorageClass: standard
Capacity: 50Mi
Access Modes: RWO
StatefulSet:
Name: mgo-init-snapshot
CreationTimestamp: Tue, 25 Sep 2018 13:06:42 +0600
Labels: kubedb.com/kind=MongoDB
kubedb.com/name=mgo-init-snapshot
Annotations: <none>
Replicas: 824641931152 desired | 1 total
Pods Status: 1 Running / 0 Waiting / 0 Succeeded / 0 Failed
Service:
Name: mgo-init-snapshot
Labels: kubedb.com/kind=MongoDB
kubedb.com/name=mgo-init-snapshot
Annotations: <none>
Type: ClusterIP
IP: 10.109.118.234
Port: db 27017/TCP
TargetPort: db/TCP
Endpoints: 172.17.0.6:27017
Service:
Name: mgo-init-snapshot-gvr
Labels: kubedb.com/kind=MongoDB
kubedb.com/name=mgo-init-snapshot
Annotations: service.alpha.kubernetes.io/tolerate-unready-endpoints=true
Type: ClusterIP
IP: None
Port: db 27017/TCP
TargetPort: 27017/TCP
Endpoints: 172.17.0.6:27017
Database Secret:
Name: mgo-init-snapshot-auth
Labels: kubedb.com/kind=MongoDB
kubedb.com/name=mgo-init-snapshot
Annotations: <none>
Type: Opaque
Data
====
password: 16 bytes
user: 4 bytes
No Snapshots.
Events:
Type Reason Age From Message
---- ------ ---- ---- -------
Normal Successful 1m MongoDB operator Successfully created Service
Normal Successful 46s MongoDB operator Successfully created StatefulSet
Normal Successful 46s MongoDB operator Successfully created MongoDB
Normal Initializing 45s MongoDB operator Initializing from Snapshot: "snapshot-infant"
Normal Successful 41s MongoDB operator Successfully patched StatefulSet
Normal Successful 41s MongoDB operator Successfully patched MongoDB
Normal SuccessfulInitialize 13s Job Controller Successfully completed initialization
Normal Successful 11s MongoDB operator Successfully patched StatefulSet
Normal Successful 11s MongoDB operator Successfully patched MongoDB
Cleaning up
To cleanup the Kubernetes resources created by this tutorial, run:
kubectl patch -n demo mg/mgo-infant mg/mgo-init-snapshot -p '{"spec":{"terminationPolicy":"WipeOut"}}' --type="merge"
kubectl delete -n demo mg/mgo-infant mg/mgo-init-snapshot
kubectl patch -n demo drmn/mgo-infant drmn/mgo-init-snapshot -p '{"spec":{"wipeOut":true}}' --type="merge"
kubectl delete -n demo drmn/mgo-infant drmn/mgo-init-snapshot
kubectl delete ns demo
Next Steps
- Monitor your MongoDB database with KubeDB using out-of-the-box CoreOS Prometheus Operator.
- Monitor your MongoDB database with KubeDB using out-of-the-box builtin-Prometheus.
- Use private Docker registry to deploy MongoDB with KubeDB.
- Detail concepts of MongoDB object.
- Detail concepts of MongoDBVersion object.
- Detail concepts of Snapshot object.
- Wondering what features are coming next? Please visit here.
- Want to hack on KubeDB? Check our contribution guidelines.