| Advisory ID | D2IQ-2021-0002 |
| Severity | Medium |
| Synopsis | Kommander fails to uninstall |
| Affected Product(s) | Konvoy |
| Affected Version(s) | 1.6, 1.7, and earlier |
| Issue date | 02-19-2021 |
| Updated on | 04-02-2021 |
Issue
There is a known problem in certain Konvoy versions where Kommander is not able to be uninstalled cleanly, and will prevent subsequent installs.
You may encounter it if you delete a Kommander pod and notice a new one is not being created in its place.
Workaround
This issue is fixed in Konvoy version 1.6.3 and 1.7.0.
For versions before those, you can run this Docker command from the same directory you run Konvoy commands. Ensure that there are no "purger" pods in the output of "kubectl get pods -n kommander" before running this:
docker run -it -v $(pwd):/opt/konvoy -e KUBECONFIG=admin.conf -w /opt/konvoy --entrypoint /bin/sh mesosphere/konvoy:v1.7.1 -c 'helm uninstall kommander-kubeaddons -n kommander --no-hooks'
After this is done, try redeploying the addons to launch Kommander again:
./konvoy deploy addons
If this does not resolve the problem, please submit a ticket with D2IQ support and we'll be happy to assist:
https://support.d2iq.com/s/article/Opening-a-New-Support-Case