You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Aug 26, 2021. It is now read-only.
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?
The text was updated successfully, but these errors were encountered:
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?
The text was updated successfully, but these errors were encountered: