In this tutorial, we will create a clone of the PostgreSQL database that has been deployed on Google Kubernetes Engine (GKE). Then we will make changes to the clone and verify that the original database has remained unaffected by changes that were done to the clone.
Before starting with this tutorial, make sure Robin Storage is installed on GKE, your PostgreSQL database is deployed, has data loaded in it, and the Helm release is registered with Robin, and you have taken a snapshot of your PostgreSQL Helm release.
We have successfully created a clone of our original PostgreSQL database, and the cloned database also has a table called “movies” with 9 rows, just like the original.
Now, let’s make changes to the clone and verify the original database remains unaffected by changes to the clone. Let’s delete the movie called “Super Troopers 2”.
Let’s verify the movie has been deleted.
You should see an output similar to the following with 8 movies.
Now, let’s connect to our original PostgreSQL database and verify it is unaffected.
Get Service IP address of our original PostgreSQL database.
Get Password of our original PostgreSQL database from Kubernetes Secret.
To verify that our PostgreSQL database is unaffected by changes to the clone, run the following command.
Let’s connect to “testdb” and check record :
You should see an output similar to the following, with all 9 movies present.
This means we can work on the original PostgreSQL database and the cloned database simultaneously without affecting each other. This is valuable for collaboration across teams where each team needs to perform a unique set of operations.
This concludes the clone PostgreSQL tutorial