WHAT
For multi az support, a 3scale Operator consumer would want to set the zone topology spread contraints for the various components installed by 3scale. This is currently not provided via the APIManager CR, and the deployment configs must be updated manually for this which would cause a subsequent pod rollout.

This can be however managed and defined via the APIManager CR.

HOW
Potentially an optional zone topology spread constraint field in the various subcomponent fields of the APIManager CRD that the reconciler will add to the pod template of the respective component

DONE

• Zone topology spread constraints for 3scale components can be defined via the APIManager CR