Delete Percona Operator for MySQL based on Percona XtraDB Cluster¶

You may have different reasons to clean up your Kubernetes environment: moving from trial deployment to a production one, testing experimental configurations and the like. In either case, you need to remove some (or all) of these objects:

Percona XtraDB Cluster managed by the Operator
Percona Operator for MySQL itself
Custom Resource Definition deployed with the Operator
Resources like PVCs and Secrets

Delete the database cluster¶

To delete the database cluster means to delete the Custom Resource associated with it.

Note

There are 3 finalizers defined in the Custom Resource, which define whether to delete or preserve TLS-related objects and data volumes when the cluster is deleted.

finalizers.percona.com/delete-ssl: if present, objects, created for SSL (Secret, certificate, and issuer) are deleted along with the cluster deletion.
finalizers.percona.com/delete-pxc-pvc: if present, Persistent Volume Claims for the database cluster Pods are deleted along with the cluster deletion.
finalizers.percona.com/delete-proxysql-pvc: if present, Persistent Volume Claims for ProxySQL Pods are deleted along with the cluster deletion.

All 3 finalizers are off by default in the deploy/cr.yaml configuration file, and this allows you to recreate the cluster without losing data, credentials for the system users, etc. You can always delete TLS-related objects and PVCs manually, if needed.

The steps are the following:

List the Custom Resources. Replace the <namespace> placeholder with your value
```
$ kubectl get pxc -n <namespace>
```
Delete the Custom Resource with the name of your cluster
```
$ kubectl delete pxc <cluster_name> -n <namespace>
```
It may take a while to stop and delete the cluster.

Sample output
```
perconaxtradbcluster.pxc.percona.com "cluster1" deleted
```

Check that the cluster is deleted by listing the Custom Resources again:

$ kubectl get pxc -n <namespace>

Sample output

No resources found in <namespace> namespace.

Delete the Operator¶

Choose the instructions relevant to the way you installed the Operator.

kubectlHelm

To uninstall the Operator, delete the Deployments related to it.

List the deployments. Replace the <namespace> placeholder with your namespace.
```
$ kubectl get deploy -n <namespace>
```

Delete the percona-* deployment

$ kubectl delete deploy percona-xtradb-cluster-operator -n <namespace>

Sample output

deployment.apps "percona-xtradb-cluster-operator" deleted

Check that the Operator is deleted by listing the Pods. As a result you should have no Pods related to it.
```
$ kubectl get pods -n <namespace>
```
Sample output
```
No resources found in <namespace> namespace.
```
If you are not just deleting the Operator and XtraDB Cluster from a specific namespace, but want to clean up your entire Kubernetes environment, you can also delete the CustomRecourceDefinitions (CRDs) .

Warning: CRDs in Kubernetes are non-namespaced but are available to the whole environment. This means that you shouldn’t delete CRDs if you still have the Operator and database cluster in some namespace.

Get the list of CRDs.
```
$ kubectl get crd
```

Delete the percona*.pxc.percona.com CRDs

$ kubectl delete crd perconaxtradbclusterbackups.pxc.percona.com perconaxtradbclusterrestores.pxc.percona.com perconaxtradbclusters.pxc.percona.com

Sample output

customresourcedefinition.apiextensions.k8s.io "perconaxtradbclusterbackups.pxc.percona.com" deleted
customresourcedefinition.apiextensions.k8s.io "perconaxtradbclusterrestores.pxc.percona.com" deleted
customresourcedefinition.apiextensions.k8s.io "perconaxtradbclusters.pxc.percona.com" deleted

To delete the Operator, do the following:

List the Helm charts:

$ helm list -n <namespace>

Sample output

cluster1    <namespace>         1           2023-10-31 10:18:10.763049 +0100 CET    deployed    pxc-db-1.17.0        1.17.0
my-op       <namespace>         1           2023-10-31 10:15:18.41444 +0100 CET     deployed    pxc-operator-1.17.0   1.17.0

Delete the release object for Percona XtraDB Cluster

$ helm uninstall cluster1 --namespace <namespace>

Delete the release object for the Operator

$ helm uninstall my-op --namespace <namespace>

Clean up resources¶

By default, TLS-related objects and data volumes remain in Kubernetes environment after you delete the cluster to allow you to recreate it without losing the data. If you wish to delete them, do the following:

Delete Persistent Volume Claims.

List PVCs. Replace the <namespace> placeholder with your namespace:

$ kubectl get pvc -n <namespace>

Sample output

NAME                     STATUS   VOLUME                                     CAPACITY   ACCESS MODES   STORAGECLASS   AGE
datadir-cluster1-pxc-0   Bound    pvc-be4e2398-6fc9-456a-836b-9f0bc36d2a16   6Gi        RWO            standard-rwo   3m57s
datadir-cluster1-pxc-1   Bound    pvc-8a9ed524-2f79-4ed1-9265-a09947084e08   6Gi        RWO            standard-rwo   2m41s
datadir-cluster1-pxc-2   Bound    pvc-830fccfb-ced6-4fab-b85a-866aa435a2c7   6Gi        RWO            standard-rwo   91s

Delete PVCs related to your cluster. The following command deletes PVCs for the cluster1 cluster:

$ kubectl delete pvc datadir-cluster1-pxc-0 datadir-cluster1-pxc-1 datadir-cluster1-pxc-2 -n <namespace>

Sample output

persistentvolumeclaim "datadir-cluster1-pxc-0" deleted
persistentvolumeclaim "datadir-cluster1-pxc-1" deleted
persistentvolumeclaim "datadir-cluster1-pxc-2" deleted

Delete the Secrets

List Secrets:
```
$ kubectl get secrets -n <namespace>
```

Delete the Secret:

$ kubectl delete secret <secret_name> -n <namespace>

Last update: 2025-04-15