Shulou(Shulou.com)05/31 Report--

This article introduces the knowledge of "how to deploy MySQL database based on Kubernetes". Many people will encounter this dilemma in the operation of actual cases, so let the editor lead you to learn how to deal with these situations. I hope you can read it carefully and be able to achieve something!

Kubernetes is an open source container orchestration engine for Google, which supports automated deployment, large-scale scalability, and application containerization management. When deploying an application in a production environment, multiple instances of the application are usually deployed to load balance application requests.

In Kubernetes, we can create multiple containers and run an application instance in each container, and then manage, discover and access this group of application instances through the built-in load balancing policy, and these details do not need to be manually configured and processed by operation and maintenance personnel.

Create a service Service

Create an IP whose Service is a fixed connection to the MySQL database to be deployed, and provide load balancer. Here are the contents of the mysql-service.yaml file:

ApiVersion: v1kind: Servicemetadata: name: mysqlspec: selector: app: mysql ports:-port: 3306

The above configuration creates a Service object named mysql that proxies requests to Pod that uses TCP port 3306 and has a label app=mysql.

Create a resource:

Kubectl create-f mysql-service.yaml

Create a persistent volume PV

Create a persistent volume mysql-pv.yaml for MySQL (Kubernetes also destroys temporary volumes when Pod no longer exists; however, Kubernetes does not destroy persistent volumes. ):

ApiVersion: v1kind: PersistentVolumemetadata: name: mysql-pv labels: type: localspec: storageClassName: manual capacity: storage: 20Gi accessModes:-ReadWriteOnce # volumes can be mounted by one node in read-write mode hostPath: path: "/ mnt/data"

Create a resource:

Kubectl create-f mysql-pv.yaml

Create persistent volume declaration PVC

Persistent volumes are resources in the cluster, and persistent volume declarations are requests for these resources and are also used to perform declaration checks on resources. Next we will create a persistent volume declaration named mysql-pvc mysql-pvc.yaml:

ApiVersion: v1kind: PersistentVolumeClaimmetadata: name: mysql-pvcspec: storageClassName: manual accessModes:-ReadWriteOnce resources: requests: storage: 20Gi

Create a resource:

Kubectl create-f mysql-pvc.yaml

Deploy MySQL

Create a Pod,mysql-deployment.yaml using a mirror of MySQL 5.7on port 3306:

ApiVersion: apps/v1kind: Deploymentmetadata: name: mysqlspec: selector: matchLabels: app: mysql strategy: type: Recreate template: metadata: labels: app: mysqlspec: containers:-image: mysql:5.7 name: mysql env:-name: MYSQL_ROOT_PASSWORD # use secret value: password in the production environment Ports:-containerPort: 3306 name: mysql volumeMounts:-name: mysql-data mountPath: / var/lib/mysql volumes:-name: mysql-data persistentVolumeClaim: claimName: mysql-pvc

Create a resource:

Kubectl create-f mysql-deployment.yaml

Connect MySQL

Kubectl run-it-- rm-- image=mysql:5.6-- restart=Never mysql-client-- mysql- hmysql-ppassword "how to deploy a MySQL database based on Kubernetes" ends here. Thank you for reading. If you want to know more about the industry, you can follow the website, the editor will output more high-quality practical articles for you!

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.