Possibility to do Canary rollouts with NGINX and to have stickiness on service level?

[florinciubotariu]

Hi.

Is this scenario possible?

I am having a stable rollout live consisting of 5 pods of an app under the same service (app-stable).
I want to do a canary release, I spin up lets say 5 pods of the canary under the app-canary service.

Now, if an user hits one of the canary pods, I want a cookie to be returned to him and the subsequent requests will always be routed to the app-canary service (and can hit any of those 5 pods).
Is this scenario possible?

It feels to me that it is not possible to:

• have stickiness on service level and not on pod level
• only a subset of users (instead of a subset of traffic) to hit the canary.
  Thanks!

The following annotations on the stable ingress are partially working in my use case but it enables stickiness on pod level on both stable / canary which I do not want.

    nginx.ingress.kubernetes.io/affinity: "cookie" 
    nginx.ingress.kubernetes.io/session-cookie-name: "routing-preference" 
    nginx.ingress.kubernetes.io/session-cookie-expires: "172800"
    nginx.ingress.kubernetes.io/session-cookie-max-age: "172800"

The only annotation I have on the canary ingress is canary-by-cookie: "routing-preference"

Thanks!

[kostis-codefresh]

Check if nginx supports the Gateway api and header based routing

See https://rollouts-plugin-trafficrouter-gatewayapi.readthedocs.io/en/latest/features/header-based-routing/