Can't scale the deployments and statefulset about tower-operator HOT 4 CLOSED

Currently, I'm not sure exactly how things will behave if you use more than one instance... some service may work okay, others may not (split-brained and all that—especially Postgres, but maybe also memcached and rabbit since they might need more config to work with more than one running pod).

But it is something that should be configurable, assuming the underlying service can scale beyond one Pod without everything breaking.

from tower-operator.

It looks like the deployments for the memcached, rabbitmq, tower_task, and tower_web are all owned by the tower resource. This is why my changes at the deployment spec for the replicas was getting automatically revert back to 1. Is there a key/value reference I can use in the tower spec to control the number of replicas for the deployments? Same question regarding the postgres statefulset.

from tower-operator.

This issue has been marked 'stale' due to lack of recent activity. If there is no further activity, the issue will be closed in another 30 days. Thank you for your contribution!

Please read this blog post to see the reasons why I mark issues as stale.

from tower-operator.

This issue is no longer marked for closure.

from tower-operator.