Allow podTemplate changes which are handled like version upgrades with a rolling re-deployment
cycle of all etcd members.
Verification
Verified on a tests cluster that I could update podTemplates with new configurations such as anti-affinity, resource requests and limits. (verified with single-node and multi-node cluster)
Also verified that version upgrades still work as before.
Changes
Verification
Refs #109 (but solved in a more generic way)