In this tutorial, we will create a clone of the CouchDB database that has been deployed on Google Kubernetes Engine (GKE). We can then alter the clone records and verify that the data from the parent database remains intact.
Before starting with this tutorial, make sure Robin Storage is installed on GKE, your CouchDB database is deployed, has data loaded in it, and the Helm release is registered with Robin and you have taken a snapshot of the CouchDB database.
We have now successfully created a clone of our original CouchDB database, and verified that the cloned database also includes the robindb with 5 records under employees document, just as it exists in the original database.
We can now alter the records of clone. This action does not impact the data in the original database. We can verify that the data in the parent database remains intact and has not changed. The Cloned database can be treated as an independent database from here onwards.
We can now snapshot the cloned database and also perform rollback operations.
This concludes the Clone CouchDB database on GKE tutorial.