StatefulSets is suitable for deploying MySQL because it provides stable network identity and persistent storage. Each Pod has an independent host name (such as mysql-0, mysql-1) for easy master-slave configuration, combined with Headless Service to implement DNS resolution, and each Pod binds a PVC to ensure data durability; the deployment steps include creating a Headless Service, defining StatefulSets, configuring environment variables, and using volumeClaimTemplates; in terms of storage, each Pod needs to allocate an independent PVC, selecting a suitable StorageClass, and ensuring that the data directory is mounted to a persistent volume; if it is highly available, you need to manually configure master-slave replication or use Operator, MySQL cluster scheme and other supplementary cluster functions.

The combination of MySQL and Kubernetes is a common requirement in many modern application architectures. StatefulSets is a controller specially used in Kubernetes to manage stateful applications. It is used to deploy MySQL, which can not only ensure the persistence of data, but also achieve certain scalability. But in actual operation, there are several key points that need attention.

1. Why StatefulSets are suitable for MySQL

As a relational database, MySQL usually requires stable network identification and persistent storage, which is the advantage of StatefulSets.

• Each Pod has a stable host name (such as mysql-0, mysql-1), which is convenient for master-slave configuration or cluster discovery.
• Combined with Headless Service, DNS resolution can be implemented to specific pods, suitable for master-slave switching or client connection.
• Each Pod corresponds to a PVC (PersistentVolumeClaim), the data is independent and will not be lost due to the restart of the Pod.

So, if you plan to deploy multiple MySQL instances on Kubernetes and want them to stay stateful and run independently, StatefulSets is a more suitable option than Deployment.

2. How to configure MySQL StatefulSet

The core steps for deploying MySQL StatefulSet include:

• Create a headless service for network identification
• Define StatefulSet and specify volumeClaimTemplates
• Set appropriate environment variables, such as MYSQL_ROOT_PASSWORD
• If you need a master-slave architecture, you also need to configure the initContainers or sidecar container for initialization

Here is a simplified version of YAML structure:

 apiVersion: v1
kind: Service
metadata:
  name: mysql
spec:
  Ports:
    - port: 3306
  clusterIP: None
---
apiVersion: apps/v1
kind: StatefulSet
metadata:
  name: mysql
spec:
  serviceName: mysql
  replicas: 3
  selector:
    matchLabels:
      app: mysql
  template:
    metadata:
      labels:
        app: mysql
    spec:
      containers:
        - name: mysql
          image: mysql:8.0
          env:
            - name: MYSQL_ROOT_PASSWORD
              value: "yourpassword"
          Ports:
            - containerPort: 3306
          volumeMounts:
            - name: mysql-data
              mountPath: /var/lib/mysql
      Volumes:
        - name: mysql-data
          persistentVolumeClaim:
            claimName: mysql-pvc

Note: This example is a single node configuration. If you want to be a master or slave, you need additional configuration scripts or use Operator.

3. Storage and persistence are key

Each Pod of the StatefulSet requires its own storage volume, which is usually defined by volumeClaimTemplates . This way, each Pod will automatically create a PVC when it starts.

• PVC StorageClass should choose the appropriate type according to your cluster environment (such as AWS's gp2, local storage, etc.)
• If you use cloud vendor services, be careful about the availability zone limitations of PVC
• Do not use emptyDir, otherwise the data will be lost after the Pod is deleted.

In addition, MySQL's data directory /var/lib/mysql must be mounted to a persistent volume, otherwise restarting the pod will cause data loss.

4. Cluster mode vs single instance deployment

Although StatefulSet can deploy multiple MySQL Pods, there is no automatic replication or clustering mechanism between them by default. That is, if you deploy three pods, it does not mean that they form a master-slave or InnoDB Cluster.

If you need high availability or automatic failover:

• You can manually configure master-slave replication (for example, use initContainer to determine whether it is a master or slave)
• Or use MySQL Operator, such as the MySQL Operator for Kubernetes provided by Oracle
• You can also consider using a solution like Percona XtraDB Cluster or Vitess

Basically that's it. StatefulSet provides a stable foundation, but MySQL cluster configuration needs to be supplemented according to business needs. Don't forget to test data persistence and network accessibility when deploying, these are the places where problems occur.

The above is the detailed content of MySQL and Kubernetes: Deploying StatefulSets for Scalability. For more information, please follow other related articles on the PHP Chinese website!