The uninstallation process might leave behind artifacts that you have to clear manually.
A service ID is created as part of installing Event Streams, which defines the identity for securing communication between internal components. To delete this service ID after uninstalling Event Streams, run the following command:
cloudctl iam service-id-delete eventstreams-<release>-service-id -f
Use the following command to find the list of IBM Event Streams objects associated with the release’s namespace:
kubectl get <type> -n <namespace> | grep ibm-es
Where type is each of
- pvc (see Note later)
There are also a number of Event Streams objects created in the kube-system namespace. To list these objects run the following command:
kubectl get pod -a -n kube-system | grep ibm-es
Note: These commands might return objects that should not be deleted. For example, do not delete secrets or system clusterroles if the kubectl output is not piped to grep.
Note: If persistent volume claims (PVCs) are deleted (the objects returned when specifying “pvc” in the commands above), the data associated with the PVCs is also deleted. This includes any persistent Kafka data on disk. Consider whether this is the desired result before deleting any PVCs.
To find which objects need to be manually cleared look for the following string in the output of the previously mentioned commands:
You can either navigate through the IBM Cloud Private cluster management console to Workloads > or Configuration > to find the objects and delete them, or use the following command:
kubectl delete <type> <name> -n <namespace>
For example, to delete a leftover
eventstreams-ibm-eventstreams-secret-copy-crb-ns, run the following command:
kubectl delete rolebinding eventstreams-ibm-eventstreams-secret-copy-crb-ns -n es
Be cautious of deleting persistent volume claims (PVCs) as the data on the disk that is associated with that persistent volume will also be deleted. This includes Event Streams message data.