Uninstall

Uninstalling StackGres clusters

Database clusters

Assuming that your cluster is running on the default namespace, execute the commands below to find and delete the clusters.

List the available clusters:

kubectl get sgcluster -n default

Will show the available SGCluster like in the following output:

NAME            AGE
my-db-cluster   4m27s

List the pods for the cluster:

kubectl get pods -n default

NAME              READY   STATUS    RESTARTS   AGE
my-db-cluster-0   5/5     Running   1          2m29s
my-db-cluster-1   5/5     Running   1          99s
my-db-cluster-2   5/5     Running   0          74s

Delete the cluster:

kubectl delete sgcluster my-db-cluster -n default

sgcluster.stackgres.io "my-db-cluster" deleted

Check if the pods were deleted:

kubectl get pods -n default

No resources found in default namespace.

Distributed Logs cluster

Assuming that your distributed logs cluster is running on the default namespace, execute the commands below to find and delete the distributed logs clusters.

List the available distributed logs clusters:

kubectl get sgdistributedlogs -n default

Will show the available SGDistributedLogs like in the following output:

NAME            AGE
my-dl-cluster   4m27s

List the pods for the cluster:

kubectl get pods -n default

NAME              READY   STATUS    RESTARTS   AGE
my-dl-cluster-0   5/5     Running   1          2m59s

Delete the distributed logs cluster:

kubectl delete sgdistributedlogs my-dl-cluster -n default

sgdistributedlogs.stackgres.io "my-dl-cluster" deleted

Check if the pods were deleted:

kubectl get pods -n default

No resources found in default namespace.

Other objects

The SGCluster depends on other objects to work properly, such as instance profiles, postgres configurations, connection pooling, object storage, backups, scripts . Execute the commands below to find and delete those objects:

List all StackGres objects:

kubectl get sgobjectstorages,sgbackups,sginstanceprofiles,sgpgconfigs,sgpoolconfigs,sgscripts -n default

NAME                                                      AGE
sgobjectstorage.stackgres.io/backup-config-minio-backend   162m

NAME                          AGE
sgbackup.stackgres.io/teste   14m

NAME                                                     AGE
sginstanceprofile.stackgres.io/instance-profile-medium   148m
sginstanceprofile.stackgres.io/instance-profile-nano     162m

NAME                                                                             AGE
sgpostgresconfig.stackgres.io/postgres-11-generated-from-default-1609855369232   162m
sgpostgresconfig.stackgres.io/postgres-11-generated-from-default-1609856085474   150m
sgpostgresconfig.stackgres.io/postgres-11-generated-from-default-1609856466466   143m
sgpostgresconfig.stackgres.io/postgres-11-generated-from-default-1609856836573   137m
sgpostgresconfig.stackgres.io/postgres-11-generated-from-default-1609857658946   124m
sgpostgresconfig.stackgres.io/postgres-11-generated-from-default-1609864032670   17m
sgpostgresconfig.stackgres.io/postgres-11-generated-from-default-1609864616518   8m6s
sgpostgresconfig.stackgres.io/postgres-12-generated-from-default-1609864589301   8m33s

NAME                                                                AGE
sgpoolingconfig.stackgres.io/generated-from-default-1609855369294   162m
sgpoolingconfig.stackgres.io/generated-from-default-1609856085523   150m
sgpoolingconfig.stackgres.io/generated-from-default-1609856466511   143m
sgpoolingconfig.stackgres.io/generated-from-default-1609856836622   137m
sgpoolingconfig.stackgres.io/generated-from-default-1609857659076   124m
sgpoolingconfig.stackgres.io/generated-from-default-1609864032716   17m
sgpoolingconfig.stackgres.io/generated-from-default-1609864589347   8m33s
sgpoolingconfig.stackgres.io/generated-from-default-1609864616550   8m6s

To delete them all:

IMPORTANT: this WILL remove the backups too! PROCEED WITH CARE.

kubectl get sgobjectstorages,sgbackups,sgclusters,sginstanceprofiles,sgpgconfigs,sgpoolconfigs,sgscripts -n default -o name | xargs kubectl delete

sgobjectstorage.stackgres.io "backup-config-minio-backend" deleted
sgbackup.stackgres.io "teste" deleted
sginstanceprofile.stackgres.io "instance-profile-medium" deleted
sginstanceprofile.stackgres.io "instance-profile-nano" deleted
sgpostgresconfig.stackgres.io "postgres-11-generated-from-default-1609855369232" deleted
sgpostgresconfig.stackgres.io "postgres-11-generated-from-default-1609856085474" deleted
sgpostgresconfig.stackgres.io "postgres-11-generated-from-default-1609856466466" deleted
sgpostgresconfig.stackgres.io "postgres-11-generated-from-default-1609856836573" deleted
sgpostgresconfig.stackgres.io "postgres-11-generated-from-default-1609857658946" deleted
sgpostgresconfig.stackgres.io "postgres-11-generated-from-default-1609864032670" deleted
sgpostgresconfig.stackgres.io "postgres-11-generated-from-default-1609864616518" deleted
sgpostgresconfig.stackgres.io "postgres-12-generated-from-default-1609864589301" deleted
sgpoolingconfig.stackgres.io "generated-from-default-1609855369294" deleted
sgpoolingconfig.stackgres.io "generated-from-default-1609856085523" deleted
sgpoolingconfig.stackgres.io "generated-from-default-1609856466511" deleted
sgpoolingconfig.stackgres.io "generated-from-default-1609856836622" deleted
sgpoolingconfig.stackgres.io "generated-from-default-1609857659076" deleted
sgpoolingconfig.stackgres.io "generated-from-default-1609864032716" deleted
sgpoolingconfig.stackgres.io "generated-from-default-1609864589347" deleted
sgpoolingconfig.stackgres.io "generated-from-default-1609864616550" deleted

Prometheus service monitors and pod monitors

The missing part are the ServiceMonitors and PodMonitors that the operator created to integrate with the Prometheus Operator.

List all StackGres ServiceMonitors and PodMonitors:

kubectl get servicemonitors,podmonitors -A -l app=StackGresCluster

NAMESPACE   NAME                                                                     AGE
stackgres   servicemonitor.monitoring.coreos.com/ui-ui-stackgres-envoy               120m
stackgres   servicemonitor.monitoring.coreos.com/ui-ui-stackgres-postgres-exporter   120m

To delete all:

kubectl get configmap -l app=StackGresCluster -o name -A | xargs kubectl delete

configmap "my-db-cluster-prometheus-postgres-exporter-config" deleted

Uninstall the Operator

Using Helm

Execute the steps below to remove the helm chart release:

## locate the namespace that the operator was installed
## our doc always points to `stackgres`
helm list --all-namespaces | grep '^\(stackgres-operator\|NAME\)\s'

Will show the installed StackGres helm chart releases like in the following output:

NAME                    NAMESPACE       REVISION        UPDATED                                 STATUS          CHART                           APP VERSION
stackgres-operator      stackgres       1               2021-01-05 10:55:09.543509648 -0300 -03 deployed        stackgres-operator-0.9.3        0.9.3

Uninstall the operator:

helm delete stackgres-operator --namespace stackgres

release "stackgres-operator" uninstalled

Ensure that there isn’t any object left on the stackgres namespace

kubectl get all -n stackgres

No resources found in stackgres namespace.

Manually

This tutorial expects that the operator was installed on the stackgres namespace. Change it if you have this installed in a different namespace.

Operator deployments

Execute the commands below to find and remove the operator deployments.

List the deployments in the stackgres namespace:

kubectl get deployments -n stackgres

Will show the installed StackGres deployments like in the following output:

NAME                 READY   UP-TO-DATE   AVAILABLE   AGE
stackgres-operator   1/1     1            1           171m
stackgres-restapi    1/1     1            1           171m

Delete the deployments in the stackgres namespace:

kubectl get deployments -n stackgres -o name | xargs kubectl delete -n stackgres

deployment.apps "stackgres-operator" deleted
deployment.apps "stackgres-restapi" deleted

Cleanup unamespaced resources

To completely remove all the

Webhooks

StackGres MutatingWebhookConfiguration and ValidatingWebhookConfiguration are the first thing to remove since they will prevent removing CRDs:

List all StackGres MutatingWebhookConfigurations and ValidatingWebhookConfigurations:

kubectl get mutatingwebhookconfiguration,validatingwebhookconfiguration | grep -F stackgres-

Will show the installed StackGres MutatingWebhookConfigurations and ValidatingWebhookConfigurations like in the following output:

mutatingwebhookconfiguration.admissionregistration.k8s.io/stackgres-operator                     2021-01-05T13:55:22Z
validatingwebhookconfiguration.admissionregistration.k8s.io/stackgres-operator                     2021-01-05T13:55:22Z

Remove all StackGres MutatingWebhookConfigurations and ValidatingWebhookConfigurations:

kubectl get mutatingwebhookconfiguration,validatingwebhookconfiguration -o name | grep stackgres- | xargs kubectl delete

mutatingwebhookconfiguration.admissionregistration.k8s.io "stackgres-operator" deleted
validatingwebhookconfiguration.admissionregistration.k8s.io "stackgres-operator" deleted

CRDs

Execute the commands below to find and remove the Custom Resource Definitions (CRDs):

## list all *.stackgres.io CRDs
kubectl get crds | grep -F .stackgres.io

Will show the installed StackGres CRDs like in the following output:

sgobjectstorages.stackgres.io               2021-01-05T13:55:07Z
sgbackups.stackgres.io                      2021-01-05T13:55:07Z
sgclusters.stackgres.io                     2021-01-05T13:55:07Z
sgdistributedlogs.stackgres.io              2021-01-05T13:55:07Z
sginstanceprofiles.stackgres.io             2021-01-05T13:55:07Z
sgpgconfigs.stackgres.io                    2021-01-05T13:55:07Z
sgpoolconfigs.stackgres.io                  2021-01-05T13:55:07Z

Delete the StackGres CRDs:

kubectl get crds -o name | grep -F .stackgres.io | xargs kubectl delete

customresourcedefinition.apiextensions.k8s.io "sgobjectstorages.stackgres.io" deleted
customresourcedefinition.apiextensions.k8s.io "sgbackups.stackgres.io" deleted
customresourcedefinition.apiextensions.k8s.io "sgclusters.stackgres.io" deleted
customresourcedefinition.apiextensions.k8s.io "sgdistributedlogs.stackgres.io" deleted
customresourcedefinition.apiextensions.k8s.io "sginstanceprofiles.stackgres.io" deleted
customresourcedefinition.apiextensions.k8s.io "sgpgconfigs.stackgres.io" deleted
customresourcedefinition.apiextensions.k8s.io "sgpoolconfigs.stackgres.io" deleted

Cluster Role Bindings

Execute the commands below to find and remove the Custom Resource Definitions (CRDs):

List all StackGres ClusterRoleBindings:

kubectl get clusterrolebinding | grep -F stackgres-

Will show the installed StackGres ClusterRoleBindings like in the following output:

stackgres-operator                                     3h14m
stackgres-restapi                                      3h14m
stackgres-restapi-admin                                3h14m

Delete the StackGres ClusterRoleBindings:

kubectl get clusterrolebinding -o name | grep stackgres- | xargs kubectl delete

clusterrolebinding.rbac.authorization.k8s.io "stackgres-operator" deleted
clusterrolebinding.rbac.authorization.k8s.io "stackgres-restapi" deleted
clusterrolebinding.rbac.authorization.k8s.io "stackgres-restapi-admin" deleted

Cluster Roles

Execute the commands below to find and remove the Custom Resource Definitions (CRDs):

List all StackGres ClusterRoles:

kubectl get clusterrole | grep -F stackgres-

Will show the installed StackGres ClusterRoles like in the following output:

stackgres-operator                                                     3h21m
stackgres-restapi                                                      3h21m

Delete all StackGres ClusterRoles:

kubectl get clusterrole -o name | grep stackgres- | xargs kubectl delete

clusterrole.rbac.authorization.k8s.io "stackgres-operator" deleted
clusterrole.rbac.authorization.k8s.io "stackgres-restapi" deleted

Namespaces

Remove the stackgres namespace:

kubectl delete namespace stackgres