Right now the operator has a field named `highAvailability`.

When you enable this field (by setting highAvailability.enabled to true) the following databases are not deployed by the operator and the operator expects them to be external:

system-redis
backend-redis
system-database

Also notice that at the moment of writing this (2020-20-04) system-memcache and zync-postgresql cannot be configured externally by the operator (nor by the templates) so they are out of the scope of this issue and any change related to them should be handled and evaluated in another issue.

This setting is an all-or-nothing setting, which does not allow you to for example deploy Redis Databases internally and the System Database externally. This is the same and inherited behaviour than in the templates.

We should allow more granularity so the user can control for those databases which ones wants to be provided by the operator and which ones wants to be deployed externally.

This issue applies to the operator and not to the templates. On the templates this is not feasible and it will not be done there. The reason for that is that in OpenShift templates resources/configuration cannot be conditionally defined, which means it would require one template for each possible combination of databases setup.

An important remark is that if we implement this issue the testing compatibility matrix increases, as until now there were all the previous databases external or all "embedded", but with the new implementation all combinations would be possible.