Install Percona Server for MySQL cluster using kubectl¶

A Kubernetes Operator is a special type of controller introduced to simplify complex deployments. The Operator extends the Kubernetes API with custom resources.

The Percona Operator for MySQL is based on best practices for configuration and setup of a Percona Server for MySQL in a Kubernetes-based environment on-premises or in the cloud.

We recommend installing the Operator with the kubectl command line utility. It is the universal way to interact with Kubernetes. Alternatively, you can install it using the Helm package manager.

Install with kubectl Install with Helm

Prerequisites¶

To install Percona Server for MySQL cluster, you need the following:

The kubectl tool to manage and deploy applications on Kubernetes, included in most Kubernetes distributions. Install not already installed, follow its official installation instructions .
A Kubernetes environment. You can deploy it on Minikube for testing purposes or using any cloud provider of your choice. Check the list of our officially supported platforms.
See also

Procedure¶

Here’s a sequence of steps to follow:

Create the Kubernetes namespace for your cluster. It is a good practice to isolate workloads in Kubernetes by installing the Operator in a custom namespace. Replace the <namespace> placeholder with your value.
```
$ kubectl create namespace <namespace>
```
Expected output
```
namespace/<namespace> was created
```

Deploy the Operator with the following command:

$ kubectl apply -f https://raw.githubusercontent.com/percona/percona-server-mysql-operator/v0.8.0/deploy/bundle.yaml  -n <namespace>

Expected output

customresourcedefinition.apiextensions.k8s.io/perconaservermysqlbackups.ps.percona.com created
customresourcedefinition.apiextensions.k8s.io/perconaservermysqlrestores.ps.percona.com created
customresourcedefinition.apiextensions.k8s.io/perconaservermysqls.ps.percona.com created
serviceaccount/percona-server-mysql-operator created
role.rbac.authorization.k8s.io/percona-server-mysql-operator-leaderelection created
role.rbac.authorization.k8s.io/percona-server-mysql-operator created
rolebinding.rbac.authorization.k8s.io/percona-server-mysql-operator-leaderelection created
rolebinding.rbac.authorization.k8s.io/percona-server-mysql-operator created
configmap/percona-server-mysql-operator-config created
deployment.apps/percona-server-mysql-operator created

As the result you will have the Operator Pod up and running.

Deploy Percona Server for MySQL cluster:

$ kubectl apply -f https://raw.githubusercontent.com/percona/percona-server-mysql-operator/v0.8.0/deploy/cr.yaml -n <namespace>

Expected output

perconaservermysql.ps.percona.com/cluster1 created

Check the Operator and the database Pods status.

$ kubectl get ps -n <namespace>

The creation process may take some time. When the process is over your cluster obtains the ready status.

Expected output

NAME       REPLICATION         ENDPOINT                   STATE   MYSQL   ORCHESTRATOR   HAPROXY   ROUTER   AGE
cluster1   group-replication   cluster1-haproxy.default   ready   3                                3        20m

You have successfully installed and deployed the Operator with default parameters.

The default configuration includes three HAProxy and three Percona Server for MySQL instances.

You can check the rest of the Operator’s parameters in the Custom Resource options reference.

Next steps¶

Connect to Percona Server for MySQL

Get expert help¶

If you need assistance, visit the community forum for comprehensive and free database knowledge, or contact our Percona Database Experts for professional support and services. Join K8S Squad to benefit from early access to features and “ask me anything” sessions with the Experts.

Community Forum Get a Percona Expert Join K8S Squad

Last update: 2024-10-29