首页 > 数据库 > Mysql > KubeSphere部署mysql

KubeSphere部署mysql的详细步骤

2024-10-14 10:22:08 作者：Try:

本文介绍了在KubeSphere中部署Mysql的详细步骤,包括创建mysql配置、pvc挂载、工作负载、服务,并测试数据库连接,步骤详尽,包括yaml配置和环境变量设置,特别强调了路径一致性和外部访问设置,还提到了使用NodePort模式解决自定义域名连接问题

演示示例使用的是3.4.1，各版本有名字差异功能是一样的由于mysql需要做数据持久化所以需要挂载数据

1.创建mysql基础配置

项目中-配置-配置字典

mysql-conf

添加键值对

[client]
default-character-set=utf8mb4
[mysql]
default-character-set=utf8mb4
[mysqld]
init_connect='SET collation_connection = utf8mb4_unicode_ci'
init_connect='SET NAMES utf8mb4'
character-set-server=utf8mb4
collation-server=utf8mb4_unicode_ci
skip-character-set-client-handshake
skip-name-resolve

贴一下yaml配置

kind: ConfigMap
apiVersion: v1
metadata:
  name: mysql-conf
  namespace: gitee
  annotations:
    kubesphere.io/creator: admin
data:
  my.cnf: |
    [client]
    default-character-set=utf8mb4
    [mysql]
    default-character-set=utf8mb4
    [mysqld]
    init_connect='SET collation_connection = utf8mb4_unicode_ci'
    init_connect='SET NAMES utf8mb4'
    character-set-server=utf8mb4
    collation-server=utf8mb4_unicode_ci
    skip-character-set-client-handshake
    skip-name-resolve

2.创建pvc挂载

项目-存储-持久卷声明

mysql-pvc

方式就选择默认
访问模式：单节点读写
大小：根据自己需要的数值增加，这里选择的是1Gb

然后直接下一步创建即可

yaml配置

kind: PersistentVolumeClaim
apiVersion: v1
metadata:
  name: mysql-pvc
  namespace: gitee
  annotations:
    kubesphere.io/creator: admin
  finalizers:
    - kubernetes.io/pvc-protection
spec:
  accessModes:
    - ReadWriteOnce
  resources:
    requests:
      storage: 1Gi
  storageClassName: local
  volumeMode: Filesystem

3.创建工作负载

应用负载-工作负载
名称：

mysql

添加容器使用的是本地私有镜像（私有镜像使用的是harbor，也可以使用其他镜像配置比较简单这里不详细说）

使用默认镜像端口并且同步主机时区

添加环境变量
设置数据库密码
MYSQL_ROOT_PASSWORD

首先挂载pvc做数据持久化
选择我们一开始创建的pvc
模式：读写
路径：/var/lib/mysql

注意：路径要一致不能错！！！

挂载配置文件
选择本教程最开始创建的字典数值
模式：只读
路径：/etc/mysql/conf.d

注意：路径要一致不能错！！！

下一步直接创建即可（如果创建失败请检查镜像是否能正常拉取）

yaml配置

kind: Deployment
apiVersion: apps/v1
metadata:
  name: mysql
  namespace: gitee
  labels:
    app: mysql
  annotations:
    deployment.kubernetes.io/revision: '1'
    kubesphere.io/creator: admin
spec:
  replicas: 1
  selector:
    matchLabels:
      app: mysql
  template:
    metadata:
      creationTimestamp: null
      labels:
        app: mysql
      annotations:
        kubesphere.io/creator: admin
        kubesphere.io/imagepullsecrets: '{"container-hrnhuh":"harbor"}'
        logging.kubesphere.io/logsidecar-config: '{}'
    spec:
      volumes:
        - name: host-time
          hostPath:
            path: /etc/localtime
            type: ''
        - name: volume-ve0oq2
          persistentVolumeClaim:
            claimName: mysql-pvc
        - name: volume-lg3r9w
          configMap:
            name: mysql-conf
            defaultMode: 420
      containers:
        - name: container-hrnhuh
          image: '192.168.21.234:81/tools/mysql:8.0.3'
          ports:
            - name: tcp-3306
              containerPort: 3306
              protocol: TCP
          env:
            - name: MYSQL_ROOT_PASSWORD
              value: '123456'
          resources:
            limits:
              cpu: '1'
              memory: 1Gi
            requests:
              cpu: '1'
              memory: 1Gi
          volumeMounts:
            - name: host-time
              readOnly: true
              mountPath: /etc/localtime
            - name: volume-ve0oq2
              mountPath: /var/lib/mysql
            - name: volume-lg3r9w
              readOnly: true
              mountPath: /etc/mysql/conf.d
          terminationMessagePath: /dev/termination-log
          terminationMessagePolicy: File
          imagePullPolicy: IfNotPresent
      restartPolicy: Always
      terminationGracePeriodSeconds: 30
      dnsPolicy: ClusterFirst
      serviceAccountName: default
      serviceAccount: default
      securityContext: {}
      imagePullSecrets:
        - name: harbor
      schedulerName: default-scheduler
  strategy:
    type: RollingUpdate
    rollingUpdate:
      maxUnavailable: 25%
      maxSurge: 25%
  revisionHistoryLimit: 10
  progressDeadlineSeconds: 600