-
Notifications
You must be signed in to change notification settings - Fork 8.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Sticky learn and Wildfly #11898
Comments
This issue is currently awaiting triage. If Ingress contributors determines this is a relevant issue, they will accept it by applying the The Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. |
|
I see. Sorry, we dont have a short or midterm to implement or accept this feature, it would demand changing lua code and accepting that the backend will tell ingress to which backend it should route, which IMO is not something we should be doing. |
For session caching (replication), a WildFly (and JBoss EAP) cluster has a primary session owner, that is reassigned when the original server is no longer available. For optimal performance, subsequent requests needs to be forwarded to this pod. This is indicated using an "affinity" cookie. Where the cookie value is set to the name of the desired server. And changes, when the primary session owner changes. |
Wildlfy sends a cookie for session affinity. Depending on the primary session owner the value of the cookie is modified to switch to another server.
How can a i respect this in the ingress configuration, normally i would use "sticky learn", but this seems not to work for the ingress controller.
Like HAProxys "preserve" keyword for cookie would be desirable.
The text was updated successfully, but these errors were encountered: