基于K8S构建MYSQL5.7-MGR集群-竹影清风阁

之前一直都主从和单主这样的架构
看了官方现在推荐的MGR集群觉得很不错，打算在测试环境一试
由于在虚拟机跑了一套很顺，今天tbaas项目组说让在K8S中跑一套，结果就躺坑了，现放出无坑版本

YAML

apiVersion: v1
kind: ConfigMap
metadata:
  name: mysql-mgr
  labels:
    app: mysql-mgr
您暂时无权查看此隐藏内容！

---

###创建一个Headless(无头)Service,就是没有clusterIP,默认访问域名是:mysql-mgr###
###podName是StatefulSet.metadata.name-序号,例如本例:mysql-mgr-0###
###服务下pod的默认访问域名是podName-Service域名,例如本例:mysql-mgr-0-mysql-mgr###
###资料参考:https://kubernetes.io/docs/concepts/workloads/controllers/statefulset/   ###
apiVersion: v1
kind: Service
metadata:
  name: mysql-mgr
  labels:
    app: mysql-mgr
spec:
  ports:
  - port: 3306
    targetPort: 3306
    name: client
  - port: 33060
    targetPort: 33060
    name: xclient
  - port: 33061
    targetPort: 33061
    name: mgr
  ###无头Service###
  clusterIP: None 
  selector:
    app: mysql-mgr
---
apiVersion: v1
kind: Service
metadata:
  name: mysql-svc
  labels:
    app: mysql-mgr
spec:
  type: NodePort
  ports:
  - port: 3306
    targetPort: 3306
    nodePort: 30306
    name: client
  selector:
    app: mysql-mgr
---
您暂时无权查看此隐藏内容！

SET SQL_LOG_BIN=0;
CREATE USER rpl_user@'%' IDENTIFIED BY 'password';
GRANT REPLICATION SLAVE ON *.* TO rpl_user@'%';
FLUSH PRIVILEGES;
SET SQL_LOG_BIN=1;

CHANGE MASTER TO MASTER_USER='rpl_user', MASTER_PASSWORD='password'  FOR CHANNEL 'group_replication_recovery';

您暂时无权查看此隐藏内容！

检查集群状态

SELECT * FROM performance_schema.replication_group_members;

其他节点执行：

SET SQL_LOG_BIN=0;
CREATE USER rpl_user@'%' IDENTIFIED BY 'password';
GRANT REPLICATION SLAVE ON *.* TO rpl_user@'%';
FLUSH PRIVILEGES;
SET SQL_LOG_BIN=1;

您暂时无权查看此隐藏内容！

生产环境案例，目前很稳定：
file