Heiko Braun, Hiram Chirino although I fixed this issue, it got me thinking. Do we, support this use case where user installs a new version with existing OpenShift resources and optionally running integration pods?

If we do, we'd have to worry about 'migrating' runtime bits as well. I saw an open PR that could change the OpenShift resource names, which could break being able to identify and stop/re-deploy existing integrations.

It should be clearly defined whether a) it's supported or not, and b) are there any loop holes for changes like resource name that might require 'migration' or handling in some other way.