Skip to content
This repository has been archived by the owner on Aug 26, 2021. It is now read-only.

SessionAffinity and nginx-ingress #52

Closed
johnparn opened this issue Oct 25, 2016 · 1 comment
Closed

SessionAffinity and nginx-ingress #52

johnparn opened this issue Oct 25, 2016 · 1 comment

Comments

@johnparn
Copy link

Hi!

I got an environment up running with two namespaces, production and staging. It is working fine with kube-lego and the nginx-ingress thanks to this project.

The other day I started a web socket server in production and all was nice and dandy. I set sessionAffinity to ClientIP for the services involved and it went smooth. When creating the second web socket server in staging, it didn't go that well. Actually, I'm not certain were the error is at the moment but I suspect when with two nginx-ingress replicas the sessionAffinity breaks. Setting the replicas of nginx-ingress to 1 will make it work.

Anyone who have had the same experience and have a recipe to get it working to have redundant nginx-ingresses?

@johnparn
Copy link
Author

Got it working by setting the enable-sticky-sessions: "true" in the configMap of the nxing-ingress and that seems to have done the trick.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant