(I work for Google, opinions are my own). GCP offers stickiness if you use their HTTPS load balancer with a feature called session affinity[0]. And the CDN sol

(I work for Google, opinions are my own). GCP offers stickiness if you use their HTTPS load balancer with a feature called session affinity[0]. And the CDN solution GCP provides also uses the HTTPS load balancer, so that sort of problem shouldn't happen (at least for your example, but it would be easy to architect it in a way that session affinity wouldnt fix the problem you described). It doesn't look like k8s has as nice of features around session affinity, it seems only to support client IP affinity. (I'm not as familiar with k8s, so feel free to correct me) There are ways out there to support this, may just depend your infrastructure. [0] https://cloud.google.com/compute/docs/load-balancing/http/#session_affinity https://cloud.google.com/compute/docs/load-balancing/http/#s...