After you restore API test data in IBM® API Connect V10.0.1, uninstall
Percona Server for MongoDB.
About this task
After your API test data is migrated, you don't need Percona Server for MongoDB (PSMDB).
Uninstall PSMDB by completing running the commands described in the following steps.
Procedure
-
Delete PSMDB, as well as the backup and restore CRs:
kubectl -n namespace delete psmdb --all
where namespace
is the namespace where PSMDB was
installed.
-
Delete the PSMDB Operator deployments:
kubectl -n namespace delete deployment percona-server-mongodb-operator
where namespace
is the namespace where PSMDB was
installed.
-
Delete the PSMDB service account:
kubectl -n namespace delete sa percona-server-mongodb-operator
where namespace
is the namespace where PSMDB was
installed.
-
Delete the PSMDB secrets:
kubectl -n namespace delete secret ibm-apiconnect-mongo-cluster-secrets
kubectl -n namespace delete secret ibm-apiconnect-mongo-cluster-ssl
kubectl -n namespace delete secret ibm-apiconnect-mongo-cluster-ssl-internal
kubectl -n namespace delete secret ibm-apiconnect-mongodb-encryption-key
where namespace
is the namespace where PSMDB was
installed.
-
Delete the PSMDB role binding:
kubectl -n namespace delete rolebindings service-account-percona-server-mongodb-operator
where namespace
is the namespace where PSMDB was
installed.
-
Delete the PSMDB roleDelete PSMDB role
kubectl -n namespace delete role
percona-server-mongodb-operator
where
namespace
is the namespace where PSMDB was installed.
-
Delete the PSMDB PVCs:
kubectl -n namespace delete pvc pvc_name
where:
-
namespace
is the namespace where PSMDB was installed.
pvc_name
is the name of a Persistent Volume Claim that is
used by PSMDB.
- The PVCs use the following naming pattern:
mongod-data-ibm-apiconnect-mongo-cluster-rs0-...
-
Delete the PSMDB CRDs:
kubectl delete crds perconaservermongodbbackubectlups.psmdb.percona.com
kubectl delete crds perconaservermongodbrestores.psmdb.percona.com
kubectl delete crds perconaservermongodbs.psmdb.percona.com