You are looking at the documentation of a prior release. To read the documentation of the latest release, please
visit here.
We use cookies and other similar technology to collect data to improve your experience on our site, as described in our Privacy Policy.
Run Production-Grade Databases on Kubernetes
Backup and Recovery Solution for Kubernetes
Run Production-Grade Vault on Kubernetes
Secure HAProxy Ingress Controller for Kubernetes
Kubernetes Configuration Syncer
Kubernetes Authentication WebHook Server
KubeDB simplifies Provision, Upgrade, Scaling, Volume Expansion, Monitor, Backup, Restore for various Databases in Kubernetes on any Public & Private Cloud
A complete Kubernetes native disaster recovery solution for backup and restore your volumes and databases in Kubernetes on any public and private clouds.
KubeVault is a Git-Ops ready, production-grade solution for deploying and configuring Hashicorp's Vault on Kubernetes.
Secure HAProxy Ingress Controller for Kubernetes
Kubernetes Configuration Syncer
Kubernetes Authentication WebHook Server
New to KubeDB? Please start here.
This tutorial will show you how to use KubeDB to initialize a MongoDB database with an existing snapshot.
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 demo
and a snapshot snapshot-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 that the yaml files that are used in this tutorial, stored in docs/examples folder in GitHub repository kubedb/cli.
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
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.8.0-beta.2/docs/examples/mongodb/Initialization/demo-2.yaml
validating "https://raw.githubusercontent.com/kubedb/cli/0.8.0-beta.2/docs/examples/mongodb/Initialization/demo-2.yaml"
mongodb "mgo-init-snapshot" created
Here,
spec.init.snapshotSource.name
refers to a Snapshot object for a MongoDB database in the same namespaces as this new mgo-init-snapshot
MongoDB 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 STATUS AGE
mgo-infant Running 24m
mgo-init-snapshot Initializing 6s
$ kubedb describe mg -n demo mgo-init-snapshot
Name: mgo-init-snapshot
Namespace: demo
StartTimestamp: Tue, 06 Feb 2018 10:34:30 +0600
Status: Running
Annotations: kubedb.com/initialized=
Volume:
StorageClass: standard
Capacity: 50Mi
Access Modes: RWO
StatefulSet:
Name: mgo-init-snapshot
Replicas: 1 current / 1 desired
CreationTimestamp: Tue, 06 Feb 2018 10:11:54 +0600
Pods Status: 1 Running / 0 Waiting / 0 Succeeded / 0 Failed
Service:
Name: mgo-init-snapshot
Type: ClusterIP
IP: 10.100.233.80
Port: db 27017/TCP
Database Secret:
Name: mgo-init-snapshot-auth
Type: Opaque
Data
====
password: 16 bytes
user: 4 bytes
No Snapshots.
Events:
FirstSeen LastSeen Count From Type Reason Message
--------- -------- ----- ---- -------- ------ -------
1m 1m 1 MongoDB operator Normal Successful Successfully patched StatefulSet
1m 1m 1 MongoDB operator Normal Successful Successfully patched MongoDB
1m 1m 1 Job Controller Normal SuccessfulInitialize Successfully completed initialization
1m 1m 1 MongoDB operator Normal Successful Successfully patched StatefulSet
1m 1m 1 MongoDB operator Normal Successful Successfully patched MongoDB
1m 1m 1 MongoDB operator Normal Initializing Initializing from Snapshot: "snapshot-infant"
1m 1m 1 MongoDB operator Normal Successful Successfully patched StatefulSet
1m 1m 1 MongoDB operator Normal Successful Successfully patched MongoDB
To cleanup the Kubernetes resources created by this tutorial, run:
$ kubedb delete mg,drmn,snap -n demo --all --force
$ kubectl delete ns demo
namespace "demo" deleted