尧图网站建设 
目录前提条件部署MySQL和WordPress编写yaml文件应用yaml文件存在问题及解决方案创建PV(持久化卷)创建一个PVC(持久化卷声明)部署添加PVC查看PV对应的主机存储删除资源查看资源删除deployment和service查看主机数据删除PVC和PV删除主机数据* *### 前提条件拥有Kubernetes集群环境可参考Kubernetes集群搭建* 理解Kubernetes部署知识可参考使用Kubernetes部署第一个应用、Deloyment控制器### 部署MySQL和WordPress#### 编写yaml文件部署mysql和wordpress需要编写对应的deployment同时需要暴露应用需要编写对应的service。为了简便这里把这些deployment和service全部编写在同一个yaml中。[rootk8s-master01 db8]# vi wordpress-mysql.yaml内容如下 apiVersion: apps/v1 kind: Deployment metadata: name: wordpress-mysql8 labels: app: wordpress-mysql8 spec: replicas: 1 selector: matchLabels: app: wordpress-mysql8 template: metadata: labels: app: wordpress-mysql8 spec: containers: - name: mysql8 image: registry.cn-hangzhou.aliyuncs.com/my-common-images/mysql:8.4.3 env: - name: MYSQL_ROOT_PASSWORD value: “your_mysql_root_password” - name: MYSQL_DATABASE value: “wordpress” - name: MYSQL_USER value: “wordpress_user” - name: MYSQL_PASSWORD value: “your_wordpress_user_password” ports: - containerPort: 3306 — apiVersion: v1 kind: Service metadata: name: wordpress-mysql8-service labels: app: wordpress-mysql8 spec: type: ClusterIP ports: - port: 3306 targetPort: 3306 selector: app: wordpress-mysql8 — apiVersion: apps/v1 kind: Deployment metadata: name: wordpress labels: app: wordpress spec: replicas: 1 selector: matchLabels: app: wordpress template: metadata: labels: app: wordpress spec: containers: - name: wordpress image: registry.cn-hangzhou.aliyuncs.com/my-common-images/wordpress:latest env: - name: WORDPRESS_DB_HOST value: wordpress-mysql8-service - name: WORDPRESS_DB_USER value: “wordpress_user” - name: WORDPRESS_DB_PASSWORD value: “your_wordpress_user_password” - name: WORDPRESS_DB_NAME value: “wordpress” ports: - containerPort: 80 — apiVersion: v1 kind: Service metadata: name: wordpress-service labels: app: wordpress spec: type: NodePort ports: - port: 80 targetPort: 80 selector: app: wordpress注意记得将your_mysql_root_password和your_wordpress_user_password替换为安全的自定义密码并且根据集群的网络和安全策略进行必要的调整如配置防火墙以允许外部访问NodePort。#### 应用yaml文件[rootk8s-master01 db8]# kubectl apply -f wordpress-mysql.yaml deployment.apps/wordpress-mysql8 createdservice/wordpress-mysql8-service createddeployment.apps/wordpress createdservice/wordpress-service created查看部署查看服务[rootk8s-master01 db8]# kubectl get deployNAME READY UP-TO-DATE AVAILABLE AGEwordpress 1/1 1 1 12swordpress-mysql8 1/1 1 1 12s[rootk8s-master01 db8]# kubectl get svcNAME TYPE CLUSTER-IP EXTERNAL-IP PORT(S) AGEkubernetes ClusterIP 10.0.0.1 443/TCP 78dwordpress-mysql8-service ClusterIP 10.15.203.40 3306/TCP 4m56swordpress-service NodePort 10.10.170.192 80:32201/TCP 4m56s看到映射的NodePort 端口为32201每个人查到的不一样以查到的端口为准浏览器访问节点ip:32201选择合适语言这里使用English为例点击Continue根据提示填写信息测试环境密码建议修改简单些便于测试。根据提示输入登录信息进入WordPress主页如下### 存在问题及解决方案存在一个问题MySQL的数据存储在Pod中如果过程中Pod被删除重建MySQL的数据也被删除了可使用PV和PVC来解决这个问题。### 创建PV(持久化卷)Kubernetes 集群中创建一个持久化卷它代表了集群中的一块存储资源可以是本地磁盘、网络存储等。以下是一个使用本地磁盘路径创建 PV 的示例假设你想将数据存储在主机的/root/datatest/mysql目录下可以根据实际情况修改这个路径创建PV的yaml文件[rootk8s-master01 db8]# vi mysql-pv.yaml内容如下 apiVersion: v1 kind: PersistentVolume metadata: name: mysql-pv spec: capacity: storage: 10Gi # 根据需求设置存储容量这里设置为10GB accessModes: - ReadWriteOnce hostPath: path: /root/datatest/mysql创建 PV[rootk8s-master01 db8]# kubectl apply -f mysql-pv.yamlpersistentvolume/mysql-pv created### 创建一个PVC(持久化卷声明)接下来创建一个持久化卷声明它用于向 Kubernetes 集群请求所需的存储资源。PVC 会与合适的 PV 进行绑定以获取实际的存储。[rootk8s-master01 db8]# vi mysql-pvc.yaml内容如下 apiVersion: v1 kind: PersistentVolumeClaim metadata: name: mysql-pvc spec: accessModes: - ReadWriteOnce resources: requests: storage: 8Gi # 根据实际需求设置请求的存储容量这里设置为8GB应小于等于PV的容量创建 PVC[rootk8s-master01 db8]# kubectl apply -f mysql-pvc.yamlpersistentvolumeclaim/mysql-pvc created### 部署添加PVC修改wordpress-mysql.yaml的MySQL Deployment在spec.template.spec.containers下的mysql8容器部分添加以下内容 volumeMounts: - name: mysql-data mountPath: /var/lib/mysql volumes: - name: mysql-data persistentVolumeClaim: claimName: mysql-pvc修改后的 完整yaml文件内容如下 apiVersion: apps/v1 kind: Deployment metadata: name: wordpress-mysql8 labels: app: wordpress-mysql8 spec: replicas: 1 selector: matchLabels: app: wordpress-mysql8 template: metadata: labels: app: wordpress-mysql8 spec: containers: - name: mysql8 image: registry.cn-hangzhou.aliyuncs.com/my-common-images/mysql:8.4.3 env: - name: MYSQL_ROOT_PASSWORD value: “your_mysql_root_password” - name: MYSQL_DATABASE value: “wordpress” - name: MYSQL_USER value: “wordpress_user” - name: MYSQL_PASSWORD value: “your_wordpress_user_password” ports: - containerPort: 3306 volumeMounts: - name: mysql-data mountPath: /var/lib/mysql volumes: - name: mysql-data persistentVolumeClaim: claimName: mysql-pvc — apiVersion: v1 kind: Service metadata: name: wordpress-mysql8-service labels: app: wordpress-mysql8 spec: type: ClusterIP ports: - port: 3306 targetPort: 3306 selector: app: wordpress-mysql8 — apiVersion: apps/v1 kind: Deployment metadata: name: wordpress labels: app: wordpress spec: replicas: 1 selector: matchLabels: app: wordpress template: metadata: labels: app: wordpress spec: containers: - name: wordpress image: registry.cn-hangzhou.aliyuncs.com/my-common-images/wordpress:latest env: - name: WORDPRESS_DB_HOST value: wordpress-mysql8-service - name: WORDPRESS_DB_USER value: “wordpress_user” - name: WORDPRESS_DB_PASSWORD value: “your_wordpress_user_password” - name: WORDPRESS_DB_NAME value: “wordpress” ports: - containerPort: 80 — apiVersion: v1 kind: Service metadata: name: wordpress-service labels: app: wordpress spec: type: NodePort ports: - port: 80 targetPort: 80 selector: app: wordpress 完成上述修改后再次执行apply命令来更新 MySQL 的部署使其使用映射到主机的持久化存储。[rootk8s-master01 db8]# kubectl apply -f wordpress-mysql.yamldeployment.apps/wordpress-mysql8 configuredservice/wordpress-mysql8-service unchangeddeployment.apps/wordpress unchangedservice/wordpress-service unchanged重新访问浏览器节点ip:32201重新根据提示设置WordPress进入WordPress主页能正常访问。### 查看PV对应的主机存储查看pod在哪台主机运行[rootk8s-master01 db8]# kubectl get pod -o wideNAME READY STATUS RESTARTS AGE IP NODE NOMINATED NODE READINESS GATESwordpress-6b69d95596-jgbnw 1/1 Running 0 53m 10.244.85.225 k8s-node01 wordpress-mysql8-64c987b8cd-vxqtk 1/1 Running 0 6m59s 10.244.85.230 k8s-node01 看到pod在k8s-node01机器运行到对应的k8s-node01机器查看pv对应的存储目录# 在运行pod的机器执行[rootk8s-node01 ~]# ls /root/datatest/mysql/‘#ib_16384_0.dblwr’ auto.cnf ca-key.pem ib_buffer_pool mysql.ibd private_key.pem sys’#ib_16384_1.dblwr’ binlog.000001 ca.pem ibdata1 mysql.sock public_key.pem undo_001’#innodb_redo’ binlog.000002 client-cert.pem ibtmp1 mysql_upgrade_history server-cert.pem undo_002’#innodb_temp’ binlog.index client-key.pem mysql performance_schema server-key.pem wordpress查看到相应的MySQL卷挂载到主机的数据。### 删除资源#### 查看资源[rootk8s-master01 db8]# kubectl get deployNAME READY UP-TO-DATE AVAILABLE AGEwordpress 1/1 1 1 81mwordpress-mysql8 1/1 1 1 81m[rootk8s-master01 db8]# kubectl get svcNAME TYPE CLUSTER-IP EXTERNAL-IP PORT(S) AGEkubernetes ClusterIP 10.0.0.1 443/TCP 78dwordpress-mysql8-service ClusterIP 10.15.203.40 3306/TCP 82mwordpress-service NodePort 10.10.170.192 80:32201/TCP 82m[rootk8s-master01 db8]# kubectl get pvNAME CAPACITY ACCESS MODES RECLAIM POLICY STATUS CLAIM STORAGECLASS VOLUMEATTRIBUTESCLASS REASON AGEmysql-pv 10Gi RWO Retain Bound default/mysql-pvc 62mmysql-pv-volume 20Gi RWO Retain Bound default/mysql-pv-claim manual 39d[rootk8s-master01 db8]# kubectl get pvcNAME STATUS VOLUME CAPACITY ACCESS MODES STORAGECLASS VOLUMEATTRIBUTESCLASS AGEmysql-pv-claim Bound mysql-pv-volume 20Gi RWO manual 39dmysql-pvc Bound mysql-pv 10Gi RWO 57m#### 删除deployment和service[rootk8s-master01 db8]# kubectl delete deploy wordpress wordpress-mysql8deployment.apps “wordpress” deleteddeployment.apps “wordpress-mysql8” deleted[rootk8s-master01 db8]# kubectl delete svc wordpress-mysql8-service wordpress-serviceservice “wordpress-mysql8-service” deletedservice “wordpress-service” deleted#### 查看主机数据查看PV对应的主机目录发现数据还在[rootk8s-node01 ~]# ls /root/datatest/mysql/‘#ib_16384_0.dblwr’ auto.cnf ca-key.pem ib_buffer_pool mysql.sock public_key.pem undo_001’#ib_16384_1.dblwr’ binlog.000001 ca.pem ibdata1 mysql_upgrade_history server-cert.pem undo_002’#innodb_redo’ binlog.000002 client-cert.pem mysql performance_schema server-key.pem wordpress’#innodb_temp’ binlog.index client-key.pem mysql.ibd private_key.pem sys#### 删除PVC和PV[rootk8s-master01 db8]# kubectl delete pvc mysql-pvcpersistentvolumeclaim “mysql-pvc” deleted[rootk8s-master01 db8]# kubectl delete pv mysql-pvpersistentvolume “mysql-pv” deleted[rootk8s-master01 db8]# kubectl get pvcNo resources found in default namespace.[rootk8s-master01 db8]# kubectl get pvNo resources found查看PV对应的主机目录数据依然存在[rootk8s-node01 ~]# ls /root/datatest/mysql/‘#ib_16384_0.dblwr’ auto.cnf ca-key.pem ib_buffer_pool mysql.sock public_key.pem undo_001’#ib_16384_1.dblwr’ binlog.000001 ca.pem ibdata1 mysql_upgrade_history server-cert.pem undo_002’#innodb_redo’ binlog.000002 client-cert.pem mysql performance_schema server-key.pem wordpress’#innodb_temp’ binlog.index client-key.pem mysql.ibd private_key.pem sys删除PV主要是从 Kubernetes 的资源管理角度进行操作它不会自动删除主机上对应的目录。这是因为PV只是对存储资源的一种抽象和管理方式它与主机文件系统是松耦合的。#### 删除主机数据如果需要删除数据并且确认这些数据是可以删除数据则需要手动删除卷挂载的主机数据。[rootk8s-node01 ~]# rm -rf /root/datatest/mysql完成enjoy it! 使用Kubernetes部署MySQL+WordPress
目录前提条件部署MySQL和WordPress编写yaml文件应用yaml文件存在问题及解决方案创建PV(持久化卷)创建一个PVC(持久化卷声明)部署添加PVC查看PV对应的主机存储删除资源查看资源删除deployment和service查看主机数据删除PVC和PV删除主机数据* *### 前提条件拥有Kubernetes集群环境可参考Kubernetes集群搭建* 理解Kubernetes部署知识可参考使用Kubernetes部署第一个应用、Deloyment控制器### 部署MySQL和WordPress#### 编写yaml文件部署mysql和wordpress需要编写对应的deployment同时需要暴露应用需要编写对应的service。为了简便这里把这些deployment和service全部编写在同一个yaml中。[rootk8s-master01 db8]# vi wordpress-mysql.yaml内容如下 apiVersion: apps/v1 kind: Deployment metadata: name: wordpress-mysql8 labels: app: wordpress-mysql8 spec: replicas: 1 selector: matchLabels: app: wordpress-mysql8 template: metadata: labels: app: wordpress-mysql8 spec: containers: - name: mysql8 image: registry.cn-hangzhou.aliyuncs.com/my-common-images/mysql:8.4.3 env: - name: MYSQL_ROOT_PASSWORD value: “your_mysql_root_password” - name: MYSQL_DATABASE value: “wordpress” - name: MYSQL_USER value: “wordpress_user” - name: MYSQL_PASSWORD value: “your_wordpress_user_password” ports: - containerPort: 3306 — apiVersion: v1 kind: Service metadata: name: wordpress-mysql8-service labels: app: wordpress-mysql8 spec: type: ClusterIP ports: - port: 3306 targetPort: 3306 selector: app: wordpress-mysql8 — apiVersion: apps/v1 kind: Deployment metadata: name: wordpress labels: app: wordpress spec: replicas: 1 selector: matchLabels: app: wordpress template: metadata: labels: app: wordpress spec: containers: - name: wordpress image: registry.cn-hangzhou.aliyuncs.com/my-common-images/wordpress:latest env: - name: WORDPRESS_DB_HOST value: wordpress-mysql8-service - name: WORDPRESS_DB_USER value: “wordpress_user” - name: WORDPRESS_DB_PASSWORD value: “your_wordpress_user_password” - name: WORDPRESS_DB_NAME value: “wordpress” ports: - containerPort: 80 — apiVersion: v1 kind: Service metadata: name: wordpress-service labels: app: wordpress spec: type: NodePort ports: - port: 80 targetPort: 80 selector: app: wordpress注意记得将your_mysql_root_password和your_wordpress_user_password替换为安全的自定义密码并且根据集群的网络和安全策略进行必要的调整如配置防火墙以允许外部访问NodePort。#### 应用yaml文件[rootk8s-master01 db8]# kubectl apply -f wordpress-mysql.yaml deployment.apps/wordpress-mysql8 createdservice/wordpress-mysql8-service createddeployment.apps/wordpress createdservice/wordpress-service created查看部署查看服务[rootk8s-master01 db8]# kubectl get deployNAME READY UP-TO-DATE AVAILABLE AGEwordpress 1/1 1 1 12swordpress-mysql8 1/1 1 1 12s[rootk8s-master01 db8]# kubectl get svcNAME TYPE CLUSTER-IP EXTERNAL-IP PORT(S) AGEkubernetes ClusterIP 10.0.0.1 443/TCP 78dwordpress-mysql8-service ClusterIP 10.15.203.40 3306/TCP 4m56swordpress-service NodePort 10.10.170.192 80:32201/TCP 4m56s看到映射的NodePort 端口为32201每个人查到的不一样以查到的端口为准浏览器访问节点ip:32201选择合适语言这里使用English为例点击Continue根据提示填写信息测试环境密码建议修改简单些便于测试。根据提示输入登录信息进入WordPress主页如下### 存在问题及解决方案存在一个问题MySQL的数据存储在Pod中如果过程中Pod被删除重建MySQL的数据也被删除了可使用PV和PVC来解决这个问题。### 创建PV(持久化卷)Kubernetes 集群中创建一个持久化卷它代表了集群中的一块存储资源可以是本地磁盘、网络存储等。以下是一个使用本地磁盘路径创建 PV 的示例假设你想将数据存储在主机的/root/datatest/mysql目录下可以根据实际情况修改这个路径创建PV的yaml文件[rootk8s-master01 db8]# vi mysql-pv.yaml内容如下 apiVersion: v1 kind: PersistentVolume metadata: name: mysql-pv spec: capacity: storage: 10Gi # 根据需求设置存储容量这里设置为10GB accessModes: - ReadWriteOnce hostPath: path: /root/datatest/mysql创建 PV[rootk8s-master01 db8]# kubectl apply -f mysql-pv.yamlpersistentvolume/mysql-pv created### 创建一个PVC(持久化卷声明)接下来创建一个持久化卷声明它用于向 Kubernetes 集群请求所需的存储资源。PVC 会与合适的 PV 进行绑定以获取实际的存储。[rootk8s-master01 db8]# vi mysql-pvc.yaml内容如下 apiVersion: v1 kind: PersistentVolumeClaim metadata: name: mysql-pvc spec: accessModes: - ReadWriteOnce resources: requests: storage: 8Gi # 根据实际需求设置请求的存储容量这里设置为8GB应小于等于PV的容量创建 PVC[rootk8s-master01 db8]# kubectl apply -f mysql-pvc.yamlpersistentvolumeclaim/mysql-pvc created### 部署添加PVC修改wordpress-mysql.yaml的MySQL Deployment在spec.template.spec.containers下的mysql8容器部分添加以下内容 volumeMounts: - name: mysql-data mountPath: /var/lib/mysql volumes: - name: mysql-data persistentVolumeClaim: claimName: mysql-pvc修改后的 完整yaml文件内容如下 apiVersion: apps/v1 kind: Deployment metadata: name: wordpress-mysql8 labels: app: wordpress-mysql8 spec: replicas: 1 selector: matchLabels: app: wordpress-mysql8 template: metadata: labels: app: wordpress-mysql8 spec: containers: - name: mysql8 image: registry.cn-hangzhou.aliyuncs.com/my-common-images/mysql:8.4.3 env: - name: MYSQL_ROOT_PASSWORD value: “your_mysql_root_password” - name: MYSQL_DATABASE value: “wordpress” - name: MYSQL_USER value: “wordpress_user” - name: MYSQL_PASSWORD value: “your_wordpress_user_password” ports: - containerPort: 3306 volumeMounts: - name: mysql-data mountPath: /var/lib/mysql volumes: - name: mysql-data persistentVolumeClaim: claimName: mysql-pvc — apiVersion: v1 kind: Service metadata: name: wordpress-mysql8-service labels: app: wordpress-mysql8 spec: type: ClusterIP ports: - port: 3306 targetPort: 3306 selector: app: wordpress-mysql8 — apiVersion: apps/v1 kind: Deployment metadata: name: wordpress labels: app: wordpress spec: replicas: 1 selector: matchLabels: app: wordpress template: metadata: labels: app: wordpress spec: containers: - name: wordpress image: registry.cn-hangzhou.aliyuncs.com/my-common-images/wordpress:latest env: - name: WORDPRESS_DB_HOST value: wordpress-mysql8-service - name: WORDPRESS_DB_USER value: “wordpress_user” - name: WORDPRESS_DB_PASSWORD value: “your_wordpress_user_password” - name: WORDPRESS_DB_NAME value: “wordpress” ports: - containerPort: 80 — apiVersion: v1 kind: Service metadata: name: wordpress-service labels: app: wordpress spec: type: NodePort ports: - port: 80 targetPort: 80 selector: app: wordpress 完成上述修改后再次执行apply命令来更新 MySQL 的部署使其使用映射到主机的持久化存储。[rootk8s-master01 db8]# kubectl apply -f wordpress-mysql.yamldeployment.apps/wordpress-mysql8 configuredservice/wordpress-mysql8-service unchangeddeployment.apps/wordpress unchangedservice/wordpress-service unchanged重新访问浏览器节点ip:32201重新根据提示设置WordPress进入WordPress主页能正常访问。### 查看PV对应的主机存储查看pod在哪台主机运行[rootk8s-master01 db8]# kubectl get pod -o wideNAME READY STATUS RESTARTS AGE IP NODE NOMINATED NODE READINESS GATESwordpress-6b69d95596-jgbnw 1/1 Running 0 53m 10.244.85.225 k8s-node01 wordpress-mysql8-64c987b8cd-vxqtk 1/1 Running 0 6m59s 10.244.85.230 k8s-node01 看到pod在k8s-node01机器运行到对应的k8s-node01机器查看pv对应的存储目录# 在运行pod的机器执行[rootk8s-node01 ~]# ls /root/datatest/mysql/‘#ib_16384_0.dblwr’ auto.cnf ca-key.pem ib_buffer_pool mysql.ibd private_key.pem sys’#ib_16384_1.dblwr’ binlog.000001 ca.pem ibdata1 mysql.sock public_key.pem undo_001’#innodb_redo’ binlog.000002 client-cert.pem ibtmp1 mysql_upgrade_history server-cert.pem undo_002’#innodb_temp’ binlog.index client-key.pem mysql performance_schema server-key.pem wordpress查看到相应的MySQL卷挂载到主机的数据。### 删除资源#### 查看资源[rootk8s-master01 db8]# kubectl get deployNAME READY UP-TO-DATE AVAILABLE AGEwordpress 1/1 1 1 81mwordpress-mysql8 1/1 1 1 81m[rootk8s-master01 db8]# kubectl get svcNAME TYPE CLUSTER-IP EXTERNAL-IP PORT(S) AGEkubernetes ClusterIP 10.0.0.1 443/TCP 78dwordpress-mysql8-service ClusterIP 10.15.203.40 3306/TCP 82mwordpress-service NodePort 10.10.170.192 80:32201/TCP 82m[rootk8s-master01 db8]# kubectl get pvNAME CAPACITY ACCESS MODES RECLAIM POLICY STATUS CLAIM STORAGECLASS VOLUMEATTRIBUTESCLASS REASON AGEmysql-pv 10Gi RWO Retain Bound default/mysql-pvc 62mmysql-pv-volume 20Gi RWO Retain Bound default/mysql-pv-claim manual 39d[rootk8s-master01 db8]# kubectl get pvcNAME STATUS VOLUME CAPACITY ACCESS MODES STORAGECLASS VOLUMEATTRIBUTESCLASS AGEmysql-pv-claim Bound mysql-pv-volume 20Gi RWO manual 39dmysql-pvc Bound mysql-pv 10Gi RWO 57m#### 删除deployment和service[rootk8s-master01 db8]# kubectl delete deploy wordpress wordpress-mysql8deployment.apps “wordpress” deleteddeployment.apps “wordpress-mysql8” deleted[rootk8s-master01 db8]# kubectl delete svc wordpress-mysql8-service wordpress-serviceservice “wordpress-mysql8-service” deletedservice “wordpress-service” deleted#### 查看主机数据查看PV对应的主机目录发现数据还在[rootk8s-node01 ~]# ls /root/datatest/mysql/‘#ib_16384_0.dblwr’ auto.cnf ca-key.pem ib_buffer_pool mysql.sock public_key.pem undo_001’#ib_16384_1.dblwr’ binlog.000001 ca.pem ibdata1 mysql_upgrade_history server-cert.pem undo_002’#innodb_redo’ binlog.000002 client-cert.pem mysql performance_schema server-key.pem wordpress’#innodb_temp’ binlog.index client-key.pem mysql.ibd private_key.pem sys#### 删除PVC和PV[rootk8s-master01 db8]# kubectl delete pvc mysql-pvcpersistentvolumeclaim “mysql-pvc” deleted[rootk8s-master01 db8]# kubectl delete pv mysql-pvpersistentvolume “mysql-pv” deleted[rootk8s-master01 db8]# kubectl get pvcNo resources found in default namespace.[rootk8s-master01 db8]# kubectl get pvNo resources found查看PV对应的主机目录数据依然存在[rootk8s-node01 ~]# ls /root/datatest/mysql/‘#ib_16384_0.dblwr’ auto.cnf ca-key.pem ib_buffer_pool mysql.sock public_key.pem undo_001’#ib_16384_1.dblwr’ binlog.000001 ca.pem ibdata1 mysql_upgrade_history server-cert.pem undo_002’#innodb_redo’ binlog.000002 client-cert.pem mysql performance_schema server-key.pem wordpress’#innodb_temp’ binlog.index client-key.pem mysql.ibd private_key.pem sys删除PV主要是从 Kubernetes 的资源管理角度进行操作它不会自动删除主机上对应的目录。这是因为PV只是对存储资源的一种抽象和管理方式它与主机文件系统是松耦合的。#### 删除主机数据如果需要删除数据并且确认这些数据是可以删除数据则需要手动删除卷挂载的主机数据。[rootk8s-node01 ~]# rm -rf /root/datatest/mysql完成enjoy it!