Uninstalling Connectware (Kubernetes)

Uninstalling Connectware removes Connectware from your system, including all containers, volumes, and service configurations.

Make sure to back up any important data before proceeding with the uninstallation, as this process will permanently remove all Connectware-related data from your system.

Prerequisites

• kubectl configured with access to the target installation

• helm version 3 installed

• <installation-name> and <namespace> (see Obtaining the Name, Namespace, and Version of your Connectware Installation)

Uninstalling Connectware

To uninstall Connectware use the helm uninstall command on your Connectware on Kubernetes installation:

helm uninstall -n <namespace> <installation-name>

Cleaning up Leftover Resources

Some resources will intentionally not be removed, like some persistent volume claims, and potentially ConfigMaps and Secrets manually created for mTLS.

If you want to completely clean up, for example for a fresh install, use this command to identify the resources:

kubectl -n <namespace> get all,cm,secret,pvc

Keep in mind that some resources are part of a standard Kubernetes namespace, for example configmap/kube-root-ca.crt or service/kubernetes. After identifying the resources for cleanup use this command to to remove them:

kubectl -n <namespace> delete <resource-1> <resource-2> <resource-n>

Example

kubectl -n <namespace> delete persistentvolumeclaim/brokerdata-broker-0
persistentvolumeclaim/brokerdata-broker-1 configmap/cw-mtls-ca-cert
secret/cw-mtls-welder-robots
persistentvolumeclaim/brokerdata-control-plane-broker-0
persistentvolumeclaim/brokerlog-control-plane-broker-0
persistentvolumeclaim/postgresql-postgresql-0
persistentvolumeclaim/certs

If you plan a fresh installation in the same location it is especially important to remove persistentvolumeclaim/postgresql-postgresql-0 and persistentvolumeclaim/certs.