Mariadb Operator using Ansible

This is mariadb operator using Ansible.

Supported features:

Basic Install
Seamless Upgrades
Backup and restore
Monitoring

TL;DR

Method 1 - Create Mariadb, Backup cronjob, Restore job and Monitor resource

$ OP=mariadb-ns
$ kubectl create namespace mariadb-ns
$ kubectl apply -f https://raw.githubusercontent.com/gunjangarge/mariadb-operator-ansible/master/deploy/crds/mariadbs.com.gunjangarge.operator.mariadb_crd.yaml
$ kubectl apply -f https://raw.githubusercontent.com/gunjangarge/mariadb-operator-ansible/master/deploy/crds/mariadbbackups.com.gunjangarge.operator.mariadb_crd.yaml
$ kubectl apply -f https://raw.githubusercontent.com/gunjangarge/mariadb-operator-ansible/master/deploy/crds/mariadbrestores.com.gunjangarge.operator.mariadb_crd.yaml
$ kubectl apply -f https://raw.githubusercontent.com/gunjangarge/mariadb-operator-ansible/master/deploy/crds/mariadbmonitors.com.gunjangarge.operator.mariadb_crd.yaml
$ kubectl apply -f https://raw.githubusercontent.com/gunjangarge/mariadb-operator-ansible/master/deploy/service_account.yaml -n $OP
$ kubectl apply -f https://raw.githubusercontent.com/gunjangarge/mariadb-operator-ansible/master/deploy/role.yaml -n $OP
$ kubectl apply -f https://raw.githubusercontent.com/gunjangarge/mariadb-operator-ansible/master/deploy/role_binding.yaml -n $OP
$ kubectl apply -f https://raw.githubusercontent.com/gunjangarge/mariadb-operator-ansible/master/deploy/operator.yaml -n $OP
$ kubectl apply -f https://raw.githubusercontent.com/gunjangarge/mariadb-operator-ansible/master/volume.yaml
$ kubectl apply -f https://raw.githubusercontent.com/gunjangarge/mariadb-operator-ansible/master/deploy/crds/com.gunjangarge.operator.mariadb_v1_mariadb_cr.yaml
$ kubectl apply -f https://raw.githubusercontent.com/gunjangarge/mariadb-operator-ansible/master/deploy/crds/com.gunjangarge.operator.mariadb_v1_mariadbbackup_cr.yaml
$ # Run only when you need to monitor database
$ kubectl apply -f https://raw.githubusercontent.com/gunjangarge/mariadb-operator-ansible/master/deploy/crds/com.gunjangarge.operator.mariadb_v1_mariadbmonitor_cr.yaml  -n $OP
$ # Run only when you need to restore database
$ # kubectl apply -f https://raw.githubusercontent.com/gunjangarge/mariadb-operator-ansible/master/deploy/crds/com.gunjangarge.operator.mariadb_v1_mariadbrestore_cr.yaml  -n $OP

Cleanup everything

Cleanup - clean up everything

Method 2 - Using create and delete resources bash script

Clone github repo and run create script

$ git clone https://github.com/gunjangarge/mariadb-operator-ansible.git
$ bash install-operator.sh
$ # bash create-resources.sh <namespace> <database service port> <database monitor port>
$ bash create-resources.sh primarydb 32000 32500
$ # for deletion
$ # bash delete-resources.sh <namespace> <database service port> <database monitor port>
$ bash delete-resources.sh primarydb 32000 32500
$ bash remove-operator.sh

Note: You can create mariadb in multiple namspaces in same K8s cluster.

Method 3 - Using github repository

Clone github repo and run following commands

$ git clone https://github.com/gunjangarge/mariadb-operator-ansible.git
$ cd mariadb-operator-ansible
$ OP=mariadb-ns
$ kubectl create namespace $OP
$ kubectl apply -f deploy/crds/mariadbs.com.gunjangarge.operator.mariadb_crd.yaml
$ kubectl apply -f deploy/crds/mariadbbackups.com.gunjangarge.operator.mariadb_crd.yaml
$ kubectl apply -f deploy/crds/mariadbrestores.com.gunjangarge.operator.mariadb_crd.yaml
$ kubectl apply -f deploy/crds/mariadbmonitors.com.gunjangarge.operator.mariadb_crd.yaml
$ kubectl apply -f deploy/service_account.yaml -n $OP
$ kubectl apply -f deploy/role.yaml -n $OP
$ kubectl apply -f deploy/role_binding.yaml -n $OP
$ kubectl apply -f deploy/operator.yaml -n $OP
$ kubectl apply -f volume.yaml
$ kubectl apply -f deploy/crds/com.gunjangarge.operator.mariadb_v1_mariadb_cr.yaml -n $OP
$ kubectl apply -f deploy/crds/com.gunjangarge.operator.mariadb_v1_mariadbbackup_cr.yaml -n $OP
$ kubectl apply -f deploy/crds/com.gunjangarge.operator.mariadb_v1_mariadbmonitor_cr.yaml -n $OP
$ # run only when you need to restore database
$ # kubectl apply -f deploy/crds/com.gunjangarge.operator.mariadb_v1_mariadbrestore_cr.yaml -n $OP

Setup Instructions

Create namespace (optional)

# kubectl create namespace mariadb-ns
namespace/mariadb-ns created

Note that if you want to create resources under a namespace, you would need to append -n <namespace> to kubectl command.

Deploy all Mariadb Operator CRDs into your cluster

$ kubectl apply -f https://raw.githubusercontent.com/gunjangarge/mariadb-operator-ansible/master/deploy/crds/mariadbs.com.gunjangarge.operator.mariadb_crd.yaml
$ kubectl apply -f https://raw.githubusercontent.com/gunjangarge/mariadb-operator-ansible/master/deploy/crds/mariadbbackups.com.gunjangarge.operator.mariadb_crd.yaml
$ kubectl apply -f https://raw.githubusercontent.com/gunjangarge/mariadb-operator-ansible/master/deploy/crds/mariadbrestores.com.gunjangarge.operator.mariadb_crd.yaml
$ kubectl apply -f https://raw.githubusercontent.com/gunjangarge/mariadb-operator-ansible/master/deploy/crds/mariadbmonitors.com.gunjangarge.operator.mariadb_crd.yaml

Verify all CRDs are deployed

$ kubectl get crds
NAME                                               CREATED AT
mariadbbackups.com.gunjangarge.operator.mariadb    2020-05-23T14:33:38Z
mariadbmonitors.com.gunjangarge.operator.mariadb   2020-05-23T14:34:13Z
mariadbrestores.com.gunjangarge.operator.mariadb   2020-05-23T14:33:59Z
mariadbs.com.gunjangarge.operator.mariadb          2020-05-23T14:33:17Z

Deploy RBAC (Service account, Roles and Operator)

$ kubectl apply -f https://raw.githubusercontent.com/gunjangarge/mariadb-operator-ansible/master/deploy/service_account.yaml
$ kubectl apply -f https://raw.githubusercontent.com/gunjangarge/mariadb-operator-ansible/master/deploy/role.yaml
$ kubectl apply -f https://raw.githubusercontent.com/gunjangarge/mariadb-operator-ansible/master/deploy/role_binding.yaml
$ kubectl apply -f https://raw.githubusercontent.com/gunjangarge/mariadb-operator-ansible/master/deploy/operator.yaml

Verify that the operator is up and running:

$ kubectl get deployment
NAME                       READY   UP-TO-DATE   AVAILABLE   AGE
mariadb-operator           1/1     1            1           5m

Create Persistent Volume for data and data backup as below

$ kubectl apply -f https://raw.githubusercontent.com/gunjangarge/mariadb-operator-ansible/master/volume.yaml

Apply Mariadb CR on cluster

$ kubectl apply -f https://raw.githubusercontent.com/gunjangarge/mariadb-operator-ansible/master/deploy/crds/com.gunjangarge.operator.mariadb_v1_mariadb_cr.yaml

Verify that the operator is up and running

$ kubectl get deployment -n mariadb-ns
NAME      READY   UP-TO-DATE   AVAILABLE   AGE
mariadb   1/1     1            1           26s

$ kubectl get pods -n mariadb-ns
NAME                       READY   STATUS    RESTARTS   AGE
mariadb-84d4f8b5dd-dqlg9   1/1     Running   0          77s

Verify that service is up

$ kubectl get svc -n mariadb-ns
NAME              TYPE       CLUSTER-IP     EXTERNAL-IP   PORT(S)          AGE
mariadb-service   NodePort   10.106.98.31   <none>        3306:32000/TCP   110s

Connect to mysql

$ mysql -h 10.0.0.7 -P 32000 -u john -pjohn123
mysql: [Warning] Using a password on the command line interface can be insecure.
Welcome to the MySQL monitor.  Commands end with ; or \g.
Your MySQL connection id is 8
Server version: 5.5.5-10.4.13-MariaDB-1:10.4.13+maria~bionic mariadb.org binary distribution

Copyright (c) 2000, 2020, Oracle and/or its affiliates. All rights reserved.

Oracle is a registered trademark of Oracle Corporation and/or its
affiliates. Other names may be trademarks of their respective
owners.

Type 'help;' or '\h' for help. Type '\c' to clear the current input statement.

mysql> show databases;
+--------------------+
| Database           |
+--------------------+
| information_schema |
| sample             |
+--------------------+
2 rows in set (0.00 sec)

mysql>

Mariadb database backup

Apply Mariadb Backup CR file

$ kubectl apply -f https://raw.githubusercontent.com/gunjangarge/mariadb-operator-ansible/master/deploy/crds/com.gunjangarge.operator.mariadb_v1_mariadbbackup_cr.yaml

Check resources in cluster

$ kubectl get all -n mariadb-ns
NAME                                            READY   STATUS      RESTARTS   AGE
pod/mariadb-backup-1589807700-5tbm8             0/1     Completed   0          25m
pod/mariadb-backup-1589808600-tc2mk             0/1     Completed   0          10m
pod/mariadb-instance-mariadb-79f94f9767-5ljl6   1/1     Running     0          35m

NAME                      TYPE       CLUSTER-IP      EXTERNAL-IP   PORT(S)          AGE
service/mariadb-service   NodePort   10.105.80.158   <none>        3306:32000/TCP   35m

NAME                                       READY   UP-TO-DATE   AVAILABLE   AGE
deployment.apps/mariadb-instance-mariadb   1/1     1            1           35m

NAME                                                  DESIRED   CURRENT   READY   AGE
replicaset.apps/mariadb-instance-mariadb-79f94f9767   1         1         1       35m

NAME                                  COMPLETIONS   DURATION   AGE
job.batch/mariadb-backup-1589807700   1/1           5s         25m
job.batch/mariadb-backup-1589808600   1/1           5s         10m

NAME                           SCHEDULE       SUSPEND   ACTIVE   LAST SCHEDULE   AGE
cronjob.batch/mariadb-backup   */15 * * * *   False     0        11m             35m

Mariadb database restore

Apply Mariadb Restore CR file

$ kubectl apply -f https://raw.githubusercontent.com/gunjangarge/mariadb-operator-ansible/master/deploy/crds/com.gunjangarge.operator.mariadb_v1_mariadbrestore_cr.yaml

Check resources from cluster

$ kubectl get all -n mariadb-ns
NAME                                    READY   STATUS      RESTARTS   AGE
pod/mariadb-backup-1589822400-qn8bs     0/1     Completed   0          108s
pod/mariadb-instance-79f94f9767-lmkp7   1/1     Running     0          3m53s
pod/mariadb-restore-d2qp9               0/1     Completed   0          43s

NAME                      TYPE       CLUSTER-IP      EXTERNAL-IP   PORT(S)          AGE
service/mariadb-service   NodePort   10.104.135.24   <none>        3306:32000/TCP   3m51s

NAME                               READY   UP-TO-DATE   AVAILABLE   AGE
deployment.apps/mariadb-instance   1/1     1            1           3m53s

NAME                                          DESIRED   CURRENT   READY   AGE
replicaset.apps/mariadb-instance-79f94f9767   1         1         1       3m53s

NAME                                  COMPLETIONS   DURATION   AGE
job.batch/mariadb-backup-1589822400   1/1           5s         108s
job.batch/mariadb-restore             1/1           4s         43s

NAME                           SCHEDULE      SUSPEND   ACTIVE   LAST SCHEDULE   AGE
cronjob.batch/mariadb-backup   */5 * * * *   False     0        117s            3m53s

Check Mariadb Operator deployment logs

$ kubectl logs -f deployment.apps/mariadb-operator

Mariadb Monitoring using Prometheus

It is assumed that Prometheus is already deployed in k8s cluster.

Deploy Prometheus Server and ServiceMonitor

$ kubectl apply -f https://raw.githubusercontent.com/gunjangarge/mariadb-operator-ansible/master/prometheus-monitoring/prometheus.yaml
$ kubectl apply -f https://raw.githubusercontent.com/gunjangarge/mariadb-operator-ansible/master/prometheus-monitoring/servicemonitor.yaml

Apply MariaDB Monitor CR file

$ kubectl apply -f https://raw.githubusercontent.com/gunjangarge/mariadb-operator-ansible/master/deploy/crds/com.gunjangarge.operator.mariadb_v1_mariadbmonitor_cr.yaml

Check resources from cluster

$ kubectl get all -n mariadb-ns
NAME                                   READY   STATUS      RESTARTS   AGE
pod/mariadb-84d4f8b5dd-8n2rf           1/1     Running     0          3h20m
pod/mariadb-backup-1590237900-ns9zs    0/1     Completed   0          37m
pod/mariadb-backup-1590238800-fmsr6    0/1     Completed   0          22m
pod/mariadb-backup-1590239700-2wfjx    0/1     Completed   0          7m47s
pod/mariadb-monitor-7dfb4d664f-mvs2h   1/1     Running     0          3h20m

NAME                              TYPE       CLUSTER-IP      EXTERNAL-IP   PORT(S)          AGE
service/mariadb-monitor-service   NodePort   10.104.94.196   <none>        9104:32500/TCP   3h20m
service/mariadb-service           NodePort   10.99.21.113    <none>        3306:32000/TCP   3h20m

NAME                              READY   UP-TO-DATE   AVAILABLE   AGE
deployment.apps/mariadb           1/1     1            1           3h20m
deployment.apps/mariadb-monitor   1/1     1            1           3h20m

NAME                                         DESIRED   CURRENT   READY   AGE
replicaset.apps/mariadb-84d4f8b5dd           1         1         1       3h20m
replicaset.apps/mariadb-monitor-7dfb4d664f   1         1         1       3h20m

NAME                                  COMPLETIONS   DURATION   AGE
job.batch/mariadb-backup-1590237900   1/1           9s         37m
job.batch/mariadb-backup-1590238800   1/1           6s         22m
job.batch/mariadb-backup-1590239700   1/1           6s         7m47s

NAME                           SCHEDULE       SUSPEND   ACTIVE   LAST SCHEDULE   AGE
cronjob.batch/mariadb-backup   */15 * * * *   False     0        7m49s           3h20m

Verify that metrics are being captured

Browse to http://mariadb-monitor-service_ip:mariadb-service-port/metrics

Cleanup

Clean up the resources:

$ kubectl delete -f https://raw.githubusercontent.com/gunjangarge/mariadb-operator-ansible/master/deploy/crds/com.gunjangarge.operator.mariadb_v1_mariadbrestore_cr.yaml -n $OP
$ kubectl delete -f https://raw.githubusercontent.com/gunjangarge/mariadb-operator-ansible/master/deploy/crds/com.gunjangarge.operator.mariadb_v1_mariadbbackup_cr.yaml -n $OP
$ kubectl delete -f https://raw.githubusercontent.com/gunjangarge/mariadb-operator-ansible/master/deploy/crds/com.gunjangarge.operator.mariadb_v1_mariadbmonitor_cr.yaml -n $OP
$ kubectl delete -f https://raw.githubusercontent.com/gunjangarge/mariadb-operator-ansible/master/deploy/crds/com.gunjangarge.operator.mariadb_v1_mariadb_cr.yaml -n $OP
$ kubectl delete -f https://raw.githubusercontent.com/gunjangarge/mariadb-operator-ansible/master/deploy/operator.yaml -n $OP
$ kubectl delete -f https://raw.githubusercontent.com/gunjangarge/mariadb-operator-ansible/master/deploy/role_binding.yaml -n $OP
$ kubectl delete -f https://raw.githubusercontent.com/gunjangarge/mariadb-operator-ansible/master/deploy/role.yaml -n $OP
$ kubectl delete -f https://raw.githubusercontent.com/gunjangarge/mariadb-operator-ansible/master/deploy/service_account.yaml -n $OP
$ kubectl delete -f https://raw.githubusercontent.com/gunjangarge/mariadb-operator-ansible/master/deploy/crds/mariadbs.com.gunjangarge.operator.mariadb_crd.yaml
$ kubectl delete -f https://raw.githubusercontent.com/gunjangarge/mariadb-operator-ansible/master/deploy/crds/mariadbmonitors.com.gunjangarge.operator.mariadb_crd.yaml
$ kubectl delete -f https://raw.githubusercontent.com/gunjangarge/mariadb-operator-ansible/master/deploy/crds/mariadbbackups.com.gunjangarge.operator.mariadb_crd.yaml
$ kubectl delete -f https://raw.githubusercontent.com/gunjangarge/mariadb-operator-ansible/master/deploy/crds/mariadbrestores.com.gunjangarge.operator.mariadb_crd.yaml
$ kubectl delete -f https://raw.githubusercontent.com/gunjangarge/mariadb-operator-ansible/master/volume.yaml
$ kubectl delete namespace mariadb-ns

Name		Name	Last commit message	Last commit date
Latest commit History 32 Commits
build		build
deploy		deploy
molecule		molecule
prometheus-monitoring		prometheus-monitoring
roles		roles
.gitignore		.gitignore
README.md		README.md
create-resources.sh		create-resources.sh
delete-resources.sh		delete-resources.sh
install-operator.sh		install-operator.sh
playbook.yaml		playbook.yaml
playbook_backup.yaml		playbook_backup.yaml
playbook_monitor.yaml		playbook_monitor.yaml
playbook_restore.yaml		playbook_restore.yaml
remove-operator.sh		remove-operator.sh
requirements.yml		requirements.yml
volume.yaml		volume.yaml
watches.yaml		watches.yaml

gunjangarge/mariadb-operator-ansible

Folders and files

Latest commit

History

Repository files navigation

Mariadb Operator using Ansible

Supported features:

TL;DR

Method 1 - Create Mariadb, Backup cronjob, Restore job and Monitor resource

Cleanup everything

Method 2 - Using create and delete resources bash script

Clone github repo and run create script

Note: You can create mariadb in multiple namspaces in same K8s cluster.

Method 3 - Using github repository

Clone github repo and run following commands

Setup Instructions

Create namespace (optional)

Deploy all Mariadb Operator CRDs into your cluster

Verify all CRDs are deployed

Deploy RBAC (Service account, Roles and Operator)

Verify that the operator is up and running:

Create Persistent Volume for data and data backup as below

Apply Mariadb CR on cluster

Verify that the operator is up and running

Verify that service is up

Connect to mysql

Mariadb database backup

Apply Mariadb Backup CR file

Check resources in cluster

Mariadb database restore

Apply Mariadb Restore CR file

Check resources from cluster

Check Mariadb Operator deployment logs

Mariadb Monitoring using Prometheus

It is assumed that Prometheus is already deployed in k8s cluster.

Deploy Prometheus Server and ServiceMonitor

Apply MariaDB Monitor CR file

Check resources from cluster

Verify that metrics are being captured

Cleanup

Clean up the resources:

About

Topics

Resources

Stars

Watchers

Forks

Releases

Packages 0

Languages

Packages