Support for Session Affinity to Traffic splitting

[shibayan]

As far as I have tested, with traffic splitting, reloading randomly accesses a different revision. To achieve A/B testing, the same user is required to access the same revision, thus session affinity is necessary.

Do you have any plans to support it?

[thara0402]

+1

[TonyHenrique]

Does Blazor Server App works on Container Apps? How would the Web Browser client <-> ContainerApp Environment know how to route to the appropriate instance when the container has more than 1 instance?

Perhaps a solution would be to have an Http Header set that would indicate the affinity to the original Container App Instance Id where this client loaded that blazor session.

Link to a discussion on Twitter thread

[quality-leftovers]

I searched for azure container apps traffic routing / splitting / sharding behavior and found nothing in the docs, but stumbled on this issue,

Would be nice, if documentation had some info on ingress traffic splitting / routing / sharding / affinity ...

[thohan88]

Based on this issue, there appears to be wide support for enabling sticky sessions in Azure Container Apps. Is this a feature on the roadmap?

[kendallroden]

Yes it is on the roadmap. we are still in the investigation phase

[torosent]

supported for single revision