For the first part of your question about the other replicas, docker will load balance between all of the replicas either with a VIP or by returning multiple IP

For the first part of your question about the other replicas, docker will load balance between all of the replicas either with a VIP or by returning multiple IPs in the DNS request[0]. I didn't check if this proxy balances across multiple records returned in a DNS request but, at least in the case of VIP-based load balancing, should work like you would expect. For the second part about updating the service, I'm a little less clear. I guess the expectation would be to bring up a differently-named service within the same network, and then `kamal-proxy deploy` it? So maybe the expectation is for service names to include a version number? Keeping the old version hot makes sense if you want to quickly be able to route back to it. [0]: https://docs.docker.com/reference/compose-file/deploy/#endpoint_mode https://docs.docker.com/reference/compose-file/deploy/#endpo...