Why does Kommander 2.X complain about requiring migration when it has been migrated successfully when I try an update

After successfully migrating (Konvoy 1.8.5 → DKP 2.1.3) Konvoy and KubeAddons as described in the D2IQ documentation, Kommander 2.1.X cli will throw the following message: 

this cluster requires migration from Konvoy 1.x. Please run kommander migrate to start the migration

if the user tries to update its configuration with the following command:

./kommander install --installer-config kommander.yaml

This happens because the Kommander cli checks for the presence of the custom resource definition (crd) “addons.kubeaddons.mesosphere.io”.

To workaround this, the user should delete the crd with the command below:

kubectl delete crd addons.kubeaddons.mesosphere.io

And then retry the kommander update/re-install:

./kommander install --installer-config kommander.yaml