Last part of the upgrade is to scale everything to 1, including komodo-server that was scaled on 0 initially.

So after the upgrade from 7.4 to 7.5, komodo is always scaled to 1. Now when I enable komodo in the CR, the operator spawns new resources, because the name was changed since 7.4 and doesn't just re-deploy the komodo server with new image, resulting in both komodo-server and syndesis-dv pods being present.

The impact on user should be minimal, as the DV should communicate only with the syndesis-dv pod.

The solution will be not to scale komodo to 1 in upgrade pod in https://github.com/syndesisio/syndesis/blob/master/tools/upgrade/steps/upgrade_60_restart_all#L18

Also this is probably only a problem when upgrading from 7.4 to 7.5, in later versions should be ok