Currently deployment handles route traffic to all replicas within a deployment regardless of version. However, this breaks semantics of application upgrades – users should be able to safely change interfaces of deployments within an application.
We should enforce that traffic within an application can only be routed between replicas of the same version. We want to always guarantee that only replicas with the same application version should be sending requests to each other.
Something to be aware of is that after the controller crashes, during the recovery period the controller will not know what code version is running on each live replica actor.
anyscalesam
commented
4 months ago
What happened + What you expected to happen
Currently deployment handles route traffic to all replicas within a deployment regardless of version. However, this breaks semantics of application upgrades – users should be able to safely change interfaces of deployments within an application.
We should enforce that traffic within an application can only be routed between replicas of the same version. We want to always guarantee that only replicas with the same application version should be sending requests to each other.
Something to be aware of is that after the controller crashes, during the recovery period the controller will not know what code version is running on each live replica actor.
Versions / Dependencies
ray 2.5
Reproduction script
n/a
Issue Severity
None