Describe the feature
For a deployment running canary in a single region the randomly generated value for the canary/primary would work as expected. But for an application running canary in two or more regions, requests with region 1 could be routed to region 2. This would result in the request hitting the canary on region 1 first, then possibly going to the canary on region 2. The proposal is to give the ability to define a static value for the cookie so requests could be region agnostic.
Proposed solution
Ability to define a static value for session affinity cookie
Any alternatives you've considered?
Describe the feature
For a deployment running canary in a single region the randomly generated value for the canary/primary would work as expected. But for an application running canary in two or more regions, requests with region 1 could be routed to region 2. This would result in the request hitting the canary on region 1 first, then possibly going to the canary on region 2. The proposal is to give the ability to define a static value for the cookie so requests could be region agnostic.
Proposed solution
Ability to define a static value for session affinity cookie
Any alternatives you've considered?