1) The document discusses automating MySQL deployments on Kubernetes using a Kubernetes Operator for MySQL Clusters that provides self-healing clusters, high availability, automated backups and restores, and other features. 2) It describes the context of Presslabs as a managed WordPress hosting company, the need for easy and scalable MySQL deployments, and their solution of developing a MySQL Operator. 3) Examples of using the MySQL Operator are provided including installing it, creating a test cluster, connecting to the cluster, scaling the cluster, and the project's current status and future plans.

1. Automating MySQL Deployments
on Kubernetes
Calin Don & Flavius Mecea
Presslabs

2. Automating MySQL
Deployments on
Kubernetes
Percona Live 2018

3. Calin Don
Co-founder & CTO
@Presslabs
Flavius Mecea
Project Lead
@Presslabs
Who are we?00.

4. Context
The Need
Solution
Use cases
Outcomes
Demo
Project status
Future plans
01.
02.
03.
04.
05.
06.
07.
08.

5. Context01.

6. WordPress
development
agency
Context01.
Managed
WordPress
hosting
Record: 2,2 BN
pageviews in a
month
Top tier in
Enterprise
hosting
Open-Source
Stack
2007 2011 2013 2015 2018

7. Context / Why Kubernetes?01.
● Ubiquitous technology
● Open-source
● The core of our Stack

8. The Need02.

9. 1. Easy MySQL Cluster deployment in Kubernetes
2. Scalable MySQL Cluster*
3. High availability for MySQL
4. Automated backups & restore
5. Built-in monitoring
The Need02.

10. The Need03.
didn’t fit our scaling model
didn’t provide enough automation

11. Solution03.

12. Kubernetes Operator for managing MySQL Clusters with
asynchronous or semi-synchronous replication.
● Self-healing clusters
● Highly available reads
● Virtually highly available writes
● Replication lag detection and mitigation
● Resource abuse control
● Automated backups and restores
Solution03.

13. How it’s made
Solution03.

14. Node internals
Solution03.

15. Percona is battle-tested in Enterprise environments.
Solution03.
● Percona XtraBackup
● Percona Toolkit
● Percona Server for MySQL
● Percona Monitoring & Management
NOW UPCOMING

16. Use Cases04.

17. ● Microservices
● Ephemeral databases for testing
● On-premise DBaaS
Use Cases04.

18. Outcomes05.

19. Outcomes / Evaluation setup05.
~ $50 ~ $50

20. Target performance vs required resources
Outcomes / Evaluation setup05.
QPS

21. Target performance vs required resources
Outcomes / Evaluation setup05.
QPS

22. Target performance vs required resources
Outcomes / Evaluation setup05.
QPS

23. Target performance vs required resources
Outcomes / Evaluation setup05.
QPS

24. Target performance vs required resources
Outcomes / Evaluation setup05.
QPS

25. ~ $50 ~ $250
Outcomes / Costs05.

26. In a cloud-native world,
room to grow is wasted
money.
Calin Don

27. Demo time!06.

28. $ helm repo add presslabs https://presslabs.github.io/charts
$ helm install presslabs/mysql-operator --name mysql-operator
Demo - install MySQL Operator

29. $ helm repo add presslabs https://presslabs.github.io/charts
$ helm install presslabs/mysql-operator --name mysql-operator
NAME: mysql-operator
LAST DEPLOYED: Fri Nov 2 12:09:24 2018
NAMESPACE: default
STATUS: DEPLOYED
...
Demo - install MySQL Operator

30. apiVersion: v1
kind: Secret
metadata:
name: test-secret
type: Opaque
data:
ROOT_PASSWORD: bm90LXNvLXNlY3VyZQ==
# USER:
# PASSWORD:
# DATABASE:
---
apiVersion: mysql.presslabs.org/v1alpha1
kind: MysqlCluster
metadata:
name: test
spec:
replicas: 1
secretName: test-secret
cluster.yamlDemo - create a cluster

31. $ kubectl apply -f cluster.yaml
secret/test-secret created
mysqlcluster.mysql.presslabs.org/test created
$ kubectl get pods
NAME READY STATUS RESTARTS
AGE
test-mysql-0 4/4 Running
2 4m
Demo - create a cluster

32. $ kubectl describe mysqlcluster test
...
Status:
Conditions:
Status: True
Type: Ready
Ready Nodes: 1
Nodes:
Name: test-mysql-0.test-mysql-nodes.default
Conditions:
- Type: Lagged
Status: Unknown
- Type: Replicating
Status: False
- Type: Master
Status: True
- Type: ReadOnly
Status: False
Demo - create a cluster

33. $ kubectl port-forward svc/test-mysql-master 3306 &
Forwarding from 127.0.0.1:3306 -> 3306
Forwarding from [::1]:3306 -> 3306
$ mysql --host=localhost -u app-user -papp-password
If you don't see a command prompt, try pressing enter.
mysql> SELECT @@hostname;
+--------------+
| @@hostname |
+--------------+
| test-mysql-0 |
+--------------+
1 row in set (0.01 sec)
Demo - connect to cluster

34. Demo - scale up
apiVersion: mysql.presslabs.org/v1alpha1
kind: MysqlCluster
metadata:
name: test
spec:
replicas: 2
secretName: test-secret
cluster.yaml

35. $ kubectl apply -f cluster.yaml
mysqlcluster.mysql.presslabs.org/test updated
Demo - scale up

36. Project status07.

37. ~250 commits, ~60 closed PRs
2nd rewrite, version 0.2.0 - is almost complete
Project status07.
Community Contributors

38. Future Plans08.

39. ● Logical mysqldump backups
● Point in time backup and restore
● Integrate Percona Management & Monitoring
● Kubernetes Service Catalog integration
● ProxySQL integration
● Vault integration
● Data encryption at rest
● GUI
Future Plans08.

40. Contribute!
github.com/presslabs/mysql-operator