Overview
KubeDB is the Kubernetes Native Database Management Solution which simplifies and automates routine database tasks such as Provisioning, Monitoring, Upgrading, Patching, Scaling, Volume Expansion, Backup, Recovery, Failure detection, and Repair for various popular databases on private and public clouds. The databases that KubeDB supports are MySQL, Kafka, MongoDB, MariaDB, Elasticsearch, Redis, PostgreSQL, ProxySQL, Percona XtraDB, Memcached and PgBouncer. You can find the guides to all the supported databases in KubeDB . In this tutorial we will Manage Highly Available and High-Performance MariaDB in in Amazon Elastic Kubernetes Service (Amazon EKS). We will cover the following steps:
- Install KubeDB
- Deploy MariaDB Clustered Database
- Horizontal Scaling of MariaDB Database
- Vertical Scaling of MariaDB Database
Get Cluster ID
We need the cluster ID to get the KubeDB License. To get cluster ID we can run the following command:
$ kubectl get ns kube-system -o jsonpath='{.metadata.uid}'
debacab3-y89q-4168-ba24-e97a553dcfa4
Get License
Go to Appscode License Server to get the license.txt file. For this tutorial we will use KubeDB Enterprise Edition.
Install KubeDB
We will use helm to install KubeDB. Please install helm here
if it is not already installed.
Now, let’s install KubeDB.
$ helm repo add appscode https://charts.appscode.com/stable/
$ helm repo update
$ helm search repo appscode/kubedb
NAME CHART VERSION APP VERSION DESCRIPTION
appscode/kubedb v2023.06.19 v2023.06.19 KubeDB by AppsCode - Production ready databases...
appscode/kubedb-autoscaler v0.19.0 v0.19.0 KubeDB Autoscaler by AppsCode - Autoscale KubeD...
appscode/kubedb-catalog v2023.06.19 v2023.06.19 KubeDB Catalog by AppsCode - Catalog for databa...
appscode/kubedb-community v0.24.2 v0.24.2 KubeDB Community by AppsCode - Community featur...
appscode/kubedb-crds v2023.06.19 v2023.06.19 KubeDB Custom Resource Definitions
appscode/kubedb-dashboard v0.10.0 v0.10.0 KubeDB Dashboard by AppsCode
appscode/kubedb-enterprise v0.11.2 v0.11.2 KubeDB Enterprise by AppsCode - Enterprise feat...
appscode/kubedb-grafana-dashboards v2023.06.19 v2023.06.19 A Helm chart for kubedb-grafana-dashboards by A...
appscode/kubedb-metrics v2023.06.19 v2023.06.19 KubeDB State Metrics
appscode/kubedb-one v2023.06.19 v2023.06.19 KubeDB and Stash by AppsCode - Production ready...
appscode/kubedb-ops-manager v0.21.0 v0.21.3 KubeDB Ops Manager by AppsCode - Enterprise fea...
appscode/kubedb-opscenter v2023.06.19 v2023.06.19 KubeDB Opscenter by AppsCode
appscode/kubedb-provisioner v0.34.0 v0.34.1 KubeDB Provisioner by AppsCode - Community feat...
appscode/kubedb-schema-manager v0.10.0 v0.10.0 KubeDB Schema Manager by AppsCode
appscode/kubedb-ui v2023.03.23 0.3.33-rc.2 A Helm chart for Kubernetes
appscode/kubedb-ui-server v2021.12.21 v2021.12.21 A Helm chart for kubedb-ui-server by AppsCode
appscode/kubedb-webhook-server v0.10.0 v0.10.0 KubeDB Webhook Server by AppsCode
# Install KubeDB Enterprise operator chart
$ helm install kubedb appscode/kubedb \
--version v2023.06.19 \
--namespace kubedb --create-namespace \
--set kubedb-provisioner.enabled=true \
--set kubedb-ops-manager.enabled=true \
--set kubedb-autoscaler.enabled=true \
--set kubedb-dashboard.enabled=true \
--set kubedb-schema-manager.enabled=true \
--set-file global.license=/path/to/the/license.txt
Let’s verify the installation:
$ watch kubectl get pods --all-namespaces -l "app.kubernetes.io/instance=kubedb"
NAMESPACE NAME READY STATUS RESTARTS AGE
kubedb kubedb-kubedb-autoscaler-659cbcb5db-x9t5c 1/1 Running 0 118s
kubedb kubedb-kubedb-dashboard-7b54f4cf5d-pjkwx 1/1 Running 0 118s
kubedb kubedb-kubedb-ops-manager-8964777bb-qkt2k 1/1 Running 0 118s
kubedb kubedb-kubedb-provisioner-7c5756c69-dg765 1/1 Running 0 118s
kubedb kubedb-kubedb-schema-manager-565fbcd959-vzv7x 1/1 Running 0 118s
kubedb kubedb-kubedb-webhook-server-958cdd86b-9nqcx 1/1 Running 0 118s
We can list the CRD Groups that have been registered by the operator by running the following command:
$ kubectl get crd -l app.kubernetes.io/name=kubedb
NAME CREATED AT
elasticsearchautoscalers.autoscaling.kubedb.com 2023-08-02T06:06:06Z
elasticsearchdashboards.dashboard.kubedb.com 2023-08-02T06:05:59Z
elasticsearches.kubedb.com 2023-08-02T06:05:59Z
elasticsearchopsrequests.ops.kubedb.com 2023-08-02T06:06:13Z
elasticsearchversions.catalog.kubedb.com 2023-08-02T06:03:29Z
etcds.kubedb.com 2023-08-02T06:06:08Z
etcdversions.catalog.kubedb.com 2023-08-02T06:03:29Z
kafkas.kubedb.com 2023-08-02T06:06:17Z
kafkaversions.catalog.kubedb.com 2023-08-02T06:03:30Z
mariadbautoscalers.autoscaling.kubedb.com 2023-08-02T06:06:06Z
mariadbdatabases.schema.kubedb.com 2023-08-02T06:06:21Z
mariadbopsrequests.ops.kubedb.com 2023-08-02T06:06:33Z
mariadbs.kubedb.com 2023-08-02T06:06:08Z
mariadbversions.catalog.kubedb.com 2023-08-02T06:03:30Z
memcacheds.kubedb.com 2023-08-02T06:06:08Z
memcachedversions.catalog.kubedb.com 2023-08-02T06:03:30Z
mongodbautoscalers.autoscaling.kubedb.com 2023-08-02T06:06:06Z
mongodbdatabases.schema.kubedb.com 2023-08-02T06:06:10Z
mongodbopsrequests.ops.kubedb.com 2023-08-02T06:06:18Z
mongodbs.kubedb.com 2023-08-02T06:06:09Z
mongodbversions.catalog.kubedb.com 2023-08-02T06:03:31Z
mysqlautoscalers.autoscaling.kubedb.com 2023-08-02T06:06:06Z
mysqldatabases.schema.kubedb.com 2023-08-02T06:06:08Z
mysqlopsrequests.ops.kubedb.com 2023-08-02T06:06:30Z
mysqls.kubedb.com 2023-08-02T06:06:09Z
mysqlversions.catalog.kubedb.com 2023-08-02T06:03:31Z
perconaxtradbautoscalers.autoscaling.kubedb.com 2023-08-02T06:06:06Z
perconaxtradbopsrequests.ops.kubedb.com 2023-08-02T06:06:47Z
perconaxtradbs.kubedb.com 2023-08-02T06:06:14Z
perconaxtradbversions.catalog.kubedb.com 2023-08-02T06:03:31Z
pgbouncers.kubedb.com 2023-08-02T06:06:15Z
pgbouncerversions.catalog.kubedb.com 2023-08-02T06:03:32Z
postgresautoscalers.autoscaling.kubedb.com 2023-08-02T06:06:06Z
postgresdatabases.schema.kubedb.com 2023-08-02T06:06:19Z
postgreses.kubedb.com 2023-08-02T06:06:15Z
postgresopsrequests.ops.kubedb.com 2023-08-02T06:06:41Z
postgresversions.catalog.kubedb.com 2023-08-02T06:03:32Z
proxysqlautoscalers.autoscaling.kubedb.com 2023-08-02T06:06:06Z
proxysqlopsrequests.ops.kubedb.com 2023-08-02T06:06:44Z
proxysqls.kubedb.com 2023-08-02T06:06:16Z
proxysqlversions.catalog.kubedb.com 2023-08-02T06:03:32Z
publishers.postgres.kubedb.com 2023-08-02T06:06:57Z
redisautoscalers.autoscaling.kubedb.com 2023-08-02T06:06:06Z
redises.kubedb.com 2023-08-02T06:06:16Z
redisopsrequests.ops.kubedb.com 2023-08-02T06:06:37Z
redissentinelautoscalers.autoscaling.kubedb.com 2023-08-02T06:06:07Z
redissentinelopsrequests.ops.kubedb.com 2023-08-02T06:06:51Z
redissentinels.kubedb.com 2023-08-02T06:06:17Z
redisversions.catalog.kubedb.com 2023-08-02T06:03:32Z
subscribers.postgres.kubedb.com 2023-08-02T06:07:01Z
Deploy MariaDB Cluster
Now, we are going to Deploy MariaDB using KubeDB. First, let’s create a Namespace in which we will deploy the database.
$ kubectl create namespace demo
namespace/demo created
Here is the yaml of the MariaDB CRO we are going to use:
apiVersion: kubedb.com/v1alpha2
kind: MariaDB
metadata:
name: mariadb-cluster
namespace: demo
spec:
version: "10.11.2"
replicas: 3
storageType: Durable
storage:
storageClassName: "gp2"
accessModes:
- ReadWriteOnce
resources:
requests:
storage: 1Gi
terminationPolicy: WipeOut
Let’s save this yaml configuration into mariadb-cluster.yaml
Then create the above MariaDB CRO
$ kubectl apply -f mariadb-cluster.yaml
mariadb.kubedb.com/mariadb-cluster created
In this yaml,
spec.versionfield specifies the version of MariaDB Here, we are using MariaDBversion 10.11.2. You can list the KubeDB supported versions of MariaDB by running$ kubectl get mariadbversioncommand.spec.storagespecifies PVC spec that will be dynamically allocated to store data for this database. This storage spec will be passed to the StatefulSet created by KubeDB operator to run database pods. You can specify any StorageClass available in your cluster with appropriate resource requests.- And the
spec.terminationPolicyfield is Wipeout means that the database will be deleted without restrictions. It can also be “Halt”, “Delete” and “DoNotTerminate”. Learn More about Termination Policy .
Once these are handled correctly and the MariaDB object is deployed, you will see that the following objects are created:
$ kubectl get all -n demo
NAME READY STATUS RESTARTS AGE
pod/mariadb-cluster-0 2/2 Running 0 102s
pod/mariadb-cluster-1 2/2 Running 0 102s
pod/mariadb-cluster-2 2/2 Running 0 102s
NAME TYPE CLUSTER-IP EXTERNAL-IP PORT(S) AGE
service/mariadb-cluster ClusterIP 10.100.207.231 <none> 3306/TCP 103s
service/mariadb-cluster-pods ClusterIP None <none> 3306/TCP 103s
NAME READY AGE
statefulset.apps/mariadb-cluster 3/3 104s
NAME TYPE VERSION AGE
appbinding.appcatalog.appscode.com/mariadb-cluster kubedb.com/mariadb 10.11.2 105s
NAME VERSION STATUS AGE
mariadb.kubedb.com/mariadb-cluster 10.11.2 Ready 112s
Let’s check if the database is ready to use,
$ kubectl get mariadb -n demo mariadb-cluster
NAME VERSION STATUS AGE
mariadb-cluster 10.11.2 Ready 2m19s
We have successfully deployed MariaDB in AWS. Now we can exec into the container to use the database.
Accessing Database Through CLI
To access the database through CLI, we have to get the credentials to access.
KubeDB will create Secret and Service for the database mariadb-cluster that we have deployed. Let’s check them using the following commands,
$ kubectl get secret -n demo -l=app.kubernetes.io/instance=mariadb-cluster
NAME TYPE DATA AGE
mariadb-cluster-auth kubernetes.io/basic-auth 2 2m48s
$ kubectl get service -n demo -l=app.kubernetes.io/instance=mariadb-cluster
NAME TYPE CLUSTER-IP EXTERNAL-IP PORT(S) AGE
mariadb-cluster ClusterIP 10.100.207.231 <none> 3306/TCP 3m7s
mariadb-cluster-pods ClusterIP None <none> 3306/TCP 3m7s
Now, we are going to use mariadb-cluster-auth to get the credentials.
$ kubectl get secrets -n demo mariadb-cluster-auth -o jsonpath='{.data.username}' | base64 -d
root
$ kubectl get secrets -n demo mariadb-cluster-auth -o jsonpath='{.data.password}' | base64 -d
l5nr!DZL!RLBbiSG
Insert Sample Data
In this section, we are going to login into our MariaDB database pod and insert some sample data.
$ kubectl exec -it mariadb-cluster-0 -n demo -c mariadb -- bash
root@mariadb-cluster-0:/# mysql --user=root --password='l5nr!DZL!RLBbiSG'
Welcome to the MariaDB monitor. Commands end with ; or \g.
Copyright (c) 2000, 2018, Oracle, MariaDB Corporation Ab and others.
Type 'help;' or '\h' for help. Type '\c' to clear the current input statement.
MariaDB [(none)]> CREATE DATABASE Music;
Query OK, 1 row affected (0.011 sec)
MariaDB [(none)]> CREATE TABLE Music.Artist (id INT(6) UNSIGNED AUTO_INCREMENT PRIMARY KEY, Name VARCHAR(50), Song VARCHAR(50));
Query OK, 0 rows affected (0.019 sec)
MariaDB [(none)]> INSERT INTO Music.Artist (Name, Song) VALUES ("Bobby Bare", "Five Hundred Miles");
Query OK, 1 row affected (0.003 sec)
MariaDB [(none)]> SELECT * FROM Music.Artist;
+----+------------+--------------------+
| id | Name | Song |
+----+------------+--------------------+
| 1 | Bobby Bare | Five Hundred Miles |
+----+------------+--------------------+
1 row in set (0.000 sec)
MariaDB [(none)]> exit
Bye
We’ve successfully inserted some sample data to our database. More information about Run & Manage Production-Grade MariaDB Database on Kubernetes can be found in MariaDB Kubernetes
Horizontal Scaling of MariaDB Cluster
Scale Up Replicas
Here, we are going to scale up the replicas of the MariaDB cluster to meet the desired number of replicas after scaling.
Before applying Horizontal Scaling, let’s check the current number of replicas,
$ kubectl get mariadb -n demo mariadb-cluster -o json | jq '.spec.replicas'
3
Let’s connect to a MariaDB instance and run this command to check the number of replicas,
$ kubectl exec -it mariadb-cluster-0 -n demo -c mariadb -- bash
root@mariadb-cluster-0:/# mysql --user=root --password='l5nr!DZL!RLBbiSG'
Welcome to the MariaDB monitor. Commands end with ; or \g.
Copyright (c) 2000, 2018, Oracle, MariaDB Corporation Ab and others.
Type 'help;' or '\h' for help. Type '\c' to clear the current input statement.
MariaDB [(none)]> SHOW STATUS LIKE 'wsrep_cluster_size';
+--------------------+-------+
| Variable_name | Value |
+--------------------+-------+
| wsrep_cluster_size | 3 |
+--------------------+-------+
1 row in set (0.001 sec)
MariaDB [(none)]> exit
Bye
Create MariaDBOpsRequest
In order to scale up the replicas of the cluster of the database, we have to create a MariaDBOpsRequest CR with our desired replicas. Let’s create it using this following yaml,
apiVersion: ops.kubedb.com/v1alpha1
kind: MariaDBOpsRequest
metadata:
name: horizontal-scale-up
namespace: demo
spec:
type: HorizontalScaling
databaseRef:
name: mariadb-cluster
horizontalScaling:
member : 5
Here,
spec.databaseRef.namespecifies that we are performing horizontal scaling operation onmariadb-clusterdatabase.spec.typespecifies that we are performingHorizontalScalingon our database.spec.horizontalScaling.memberspecifies the desired replicas after scaling.
Let’s save this yaml configuration into horizontal-scale-up.yaml and apply it,
$ kubectl apply -f horizontal-scale-up.yaml
mariadbopsrequest.ops.kubedb.com/horizontal-scale-up created
Let’s wait for MariaDBOpsRequest STATUS to be Successful. Run the following command to watch MariaDBOpsRequest CR,
$ watch kubectl get mariadbopsrequest -n demo
NAME TYPE STATUS AGE
horizontal-scale-up HorizontalScaling Successful 3m54s
We can see from the above output that the MariaDBOpsRequest has succeeded. Now, we are going to verify the number of replicas,
$ kubectl get mariadb -n demo mariadb-cluster -o json | jq '.spec.replicas'
5
Let’s connect to a MariaDB instance and run this command to check the number of replicas,
$ kubectl exec -it mariadb-cluster-0 -n demo -c mariadb -- bash
root@mariadb-cluster-0:/# mysql --user=root --password='l5nr!DZL!RLBbiSG'
Welcome to the MariaDB monitor. Commands end with ; or \g.
Copyright (c) 2000, 2018, Oracle, MariaDB Corporation Ab and others.
Type 'help;' or '\h' for help. Type '\c' to clear the current input statement.
MariaDB [(none)]> SHOW STATUS LIKE 'wsrep_cluster_size';
+--------------------+-------+
| Variable_name | Value |
+--------------------+-------+
| wsrep_cluster_size | 5 |
+--------------------+-------+
1 row in set (0.001 sec)
MariaDB [(none)]> exit
Bye
From all the above outputs we can see that the replicas of the cluster is now increased to 5. That means we have successfully scaled up the replicas of the MariaDB cluster.
Scale Down Replicas
Here, we are going to scale down the replicas of the cluster to meet the desired number of replicas after scaling.
Create MariaDBOpsRequest
In order to scale down the cluster of the database, we need to create a MariaDBOpsRequest CR with our desired replicas. Let’s create it using this following yaml,
apiVersion: ops.kubedb.com/v1alpha1
kind: MariaDBOpsRequest
metadata:
name: horizontal-scale-down
namespace: demo
spec:
type: HorizontalScaling
databaseRef:
name: mariadb-cluster
horizontalScaling:
member : 3
Here,
spec.databaseRef.namespecifies that we are performing horizontal scaling operation onmariadb-clusterdatabase.spec.typespecifies that we are performingHorizontalScalingon our database.spec.horizontalScaling.memberspecifies the desired replicas after scaling.
Let’s save this yaml configuration into horizontal-scale-down.yaml and apply it,
$ kubectl apply -f horizontal-scale-down.yaml
mariadbopsrequest.ops.kubedb.com/horizontal-scale-down created
Let’s wait for MariaDBOpsRequest STATUS to be Successful. Run the following command to watch MariaDBOpsRequest CR,
$ watch kubectl get mariadbopsrequest -n demo
NAME TYPE STATUS AGE
horizontal-scale-down HorizontalScaling Successful 3m59s
We can see from the above output that the MariaDBOpsRequest has succeeded. Now, we are going to verify the number of replicas,
$ kubectl get mariadb -n demo mariadb-cluster -o json | jq '.spec.replicas'
3
Let’s connect to a MariaDB instance and run this command to check the number of replicas,
$ kubectl exec -it mariadb-cluster-0 -n demo -c mariadb -- bash
root@mariadb-cluster-0:/# mysql --user=root --password='l5nr!DZL!RLBbiSG'
Welcome to the MariaDB monitor. Commands end with ; or \g.
Copyright (c) 2000, 2018, Oracle, MariaDB Corporation Ab and others.
Type 'help;' or '\h' for help. Type '\c' to clear the current input statement.
MariaDB [(none)]> SHOW STATUS LIKE 'wsrep_cluster_size';
+--------------------+-------+
| Variable_name | Value |
+--------------------+-------+
| wsrep_cluster_size | 3 |
+--------------------+-------+
1 row in set (0.001 sec)
MariaDB [(none)]> exit
Bye
From all the above outputs we can see that the replicas of the cluster is decreased to 3. That means we have successfully scaled down the replicas of the MariaDB cluster.
Vetical Scaling of MariaDB Cluster
Here, we are going to scale up the current cpu resource of the MariaDB cluster by applying Vertical Scaling. Before applying it, let’s check the current resources,
$ kubectl get pod -n demo mariadb-cluster-0 -o json | jq '.spec.containers[].resources'
{
"limits": {
"memory": "1Gi"
},
"requests": {
"cpu": "500m",
"memory": "1Gi"
}
}
Vertical Scale Up
Create MariaDBOpsRequest
In order to update the resources of the database, we have to create a MariaDBOpsRequest CR with our desired resources. Let’s create it using this following yaml,
apiVersion: ops.kubedb.com/v1alpha1
kind: MariaDBOpsRequest
metadata:
name: vertical-scale-up
namespace: demo
spec:
type: VerticalScaling
databaseRef:
name: mariadb-cluster
verticalScaling:
mariadb:
requests:
memory: "1.5Gi"
cpu: "0.7"
limits:
memory: "1.5Gi"
cpu: "0.7"
Here,
spec.databaseRef.namespecifies that we are performing vertical scaling operation onmariadb-clusterdatabase.spec.typespecifies that we are performingVerticalScalingon our database.spec.VerticalScaling.mariadbspecifies the desired resources after scaling.
Let’s save this yaml configuration into vertical-scale.yaml and apply it,
$ kubectl apply -f vertical-scale-up.yaml
mariadbopsrequest.ops.kubedb.com/vertical-scale-up created
Let’s wait for MariaDBOpsRequest STATUS to be Successful. Run the following command to watch MariaDBOpsRequest CR,
$ watch kubectl get mariadbopsrequest -n demo
NAME TYPE STATUS AGE
vertical-scale-up VerticalScaling Successful 3m57s
We can see from the above output that the MariaDBOpsRequest has succeeded. Now, we are going to verify from one of the Pod yaml whether the resources of the database has updated to meet up the desired state. Let’s check with the following command,
$ kubectl get pod -n demo mariadb-cluster-0 -o json | jq '.spec.containers[].resources'
{
"limits": {
"cpu": "700m",
"memory": "1536Mi"
},
"requests": {
"cpu": "700m",
"memory": "1536Mi"
}
}
The above output verifies that we have successfully scaled up the resources of the MariaDB database.
Vertical Scale Down
Create MariaDBOpsRequest
In order to scale down the resources of the database, we have to create a MariaDBOpsRequest CR with our desired resources. Let’s create it using this following yaml,
apiVersion: ops.kubedb.com/v1alpha1
kind: MariaDBOpsRequest
metadata:
name: vertical-scale-down
namespace: demo
spec:
type: VerticalScaling
databaseRef:
name: mariadb-cluster
verticalScaling:
mariadb:
requests:
memory: "1Gi"
cpu: "0.5"
limits:
memory: "1Gi"
cpu: "0.5"
In this yaml,
spec.databaseRef.namespecifies that we are performing vertical scaling operation onmariadb-clusterdatabase.spec.typespecifies that we are performingVerticalScalingon our database.spec.verticalScaling.mariadbspecifies the desired resources after scaling.
Let’s save this yaml configuration into vertical-scale-down.yaml and apply it,
$ kubectl apply -f vertical-scale-down.yaml
mariadbopsrequest.ops.kubedb.com/vertical-scale-down created
Let’s wait for MariaDBOpsRequest STATUS to be Successful. Run the following command to watch MariaDBOpsRequest CR,
$ kubectl get mariadbopsrequest -n demo
NAME TYPE STATUS AGE
vertical-scale-down VerticalScaling Successful 2m52s
We can see from the above output that the MariaDBOpsRequest has succeeded. Now, we are going to verify from one of the Pod yaml whether the resources of the database has updated to meet up the desired state. Let’s check with the following command,
$ kubectl get pod -n demo mariadb-cluster-0 -o json | jq '.spec.containers[].resources'
{
"limits": {
"cpu": "500m",
"memory": "1Gi"
},
"requests": {
"cpu": "500m",
"memory": "1Gi"
}
}
The above output verifies that we have successfully scaled down the resources of the MariaDB cluster.
We have made an in depth tutorial on MariaDB Alerting and Multi-Tenancy Support by using KubeDB. You can have a look into the video below:
Support
To speak with us, please leave a message on our website .
To receive product announcements, follow us on Twitter .
To watch tutorials of various Production-Grade Kubernetes Tools Subscribe our YouTube channel.
More about MariaDB in Kubernetes
If you have found a bug with KubeDB or want to request for new features, please file an issue .