Operator currently supports only 1 deployment per components and that creates a blocker for achieving few things as below.
- Currently we can't separate out replicas and (all of it resources) by AZs. (having pods of same replicas across AZ is not perf/cost efficient and also not reliable)
- Be able to have independent deployment/pods unit per replica. having common deployment across replicas creates lot of segment balancing and movement churn (specially when hpas adds/remove pods and creating/reducing replicas).
To be able to create multiple deployments will help get those scheduled as per AZ needs and also use those as a resource groups host to be able to achieve replica isolation support.
Operator currently supports only 1 deployment per components and that creates a blocker for achieving few things as below.
To be able to create multiple deployments will help get those scheduled as per AZ needs and also use those as a resource groups host to be able to achieve replica isolation support.