Consumers of ClusterPools have discovered an unintended benefit: they're a convenient way to "template" ClusterDeployments.
This has led to a few interesting edge cases, such as using [zero-size pools](https://issues.redhat.com/browse/HIVE-1593) to get this templating behavior without actually using or caring about any of the intended pool-ish features.
Having a separate ClusterTemplate mechanism for creating ClusterDeployments would satisfy this use case without having to retrofit ClusterPools for this purpose.

Another pool-related motivation for this is that we continue to find use cases for adding more of the ClusterDeployment config fields to ClusterPools.
Each time this comes up we have to discuss whether it's worth expanding the ClusterPool spec for this field; and the duplication is just generally uncomfortable.
A ClusterTemplate object would provide a single source for all the configurable fields of ClusterDeployment.
The two would by definition be in sync from the start; and any time we decided to add a field it would automatically be available for both ClusterPools and ClusterDeployments.