You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi! While looking at Zulip, I noticed that (https://github.com/zulip/docker-zulip/blob/master/kubernetes/zulip-rc.yml)[the kubernetes example provided in this repo] had one replication controller for everything.
Being used to things being done a bit differently, I'm wondering, what is the rationale with putting all the stack into that single resource? Wouldn't it make sense to have separate statefulsets/deployments instead?
The text was updated successfully, but these errors were encountered:
Hi! While looking at Zulip, I noticed that (https://github.com/zulip/docker-zulip/blob/master/kubernetes/zulip-rc.yml)[the kubernetes example provided in this repo] had one replication controller for everything.
Being used to things being done a bit differently, I'm wondering, what is the rationale with putting all the stack into that single resource? Wouldn't it make sense to have separate statefulsets/deployments instead?
The text was updated successfully, but these errors were encountered: