We have discovered the following behaviour: When the host template contains an cluster zone entry, it overides the cluster zone entry of a service template. E.g. the service is configured to be executed in the master zone but the host has the zone "satzone1". Then the service itself is executed in "satzone1" as well.
We have no problem with this behaviour, in fact we are happy with it. We are concerned that this behaviour is just "as it is".
Is this behaviour knowingly designed or will it possibly change in the future? (I didn't find any hints in the documentation).
If it is planned I would suggest to amend the documentation.