In this tutorial, we will create a clone of the MariaDB 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 MariaDB database is deployed, has data loaded in it, and the Helm release is registered with Robin, and you have taken a snapshot of your MariaDB Helm release.
We have successfully created a clone of our original MariaDB 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 MariaDB database and verify it is unaffected.
Get Service IP address of our original MariaDB database.
Get Password of our original MariaDB database from Kubernetes Secret.
To verify that our MariaDB database is unaffected by changes to the clone, run the following command.
You should see an output similar to the following, with all 9 movies present.
As you can see from the output above, our original MariaDB database only 9 movies and hence was unaffected by the data deletion in the clone.
This means we can work on the original MariaDB database and the cloned database simultaneously without them affecting each other. This is valuable for collaboration across teams where each team needs to perform unique sets of operations.
This concludes the clone MariaDB on GKE tutorial.