How to handle multiple Fuse app instances in an openshift domain

Currently the fuse cartridge uses domain environment variables to link together multiple fuse applications created in a single openshift domain. (The first fuse app creates the domain env variables, additional fuse applications see the existing env variable and rather than create new domain env variables, they use the existing ones to configure themselves and link to the first fuse app instance).

However there is a limitation in how domain environment variables function in openshift: Their lifecycle is tied to the application that created them.

This means that if I create "fuse1", "fuse2", "fuse3" and then delete fuse1, the domain environment variables will be deleted.

(In addition, fuse2 and fuse3 were originally configured to point to fuse1 which no longer exists).

The question is, what is the expected and desired behavior for multiple fuse applications in a domain?

1) We could remove the clustering behavior entirely and treat each fuse app as its own fabric (no domain env variables)
2) We can put the warning in place that you should not remove "fuse1" before removing all other fuse application instances in a domain