-
Notifications
You must be signed in to change notification settings - Fork 8.3k
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
if alternate access two ingress paths, the session can't keep sticky #1930
Comments
I solve that use two "ingress.kubernetes.io/session-cookie-name: k8s-X" |
yes, have same problem, and i found where the problem is in code:
it does not use all parameters from nginx-sticky-module-ng |
…ple rules and backends * for an ingress with session affinity cookie, set the location as path on the cookie when unique * the previous behaviour ( cookie path=/ ) is preserved for ingresses with multiple rules for the same backend (locations not unique)
Issues go stale after 90d of inactivity. If this issue is safe to close now please do so with Send feedback to sig-testing, kubernetes/test-infra and/or fejta. |
Stale issues rot after 30d of inactivity. If this issue is safe to close now please do so with Send feedback to sig-testing, kubernetes/test-infra and/or fejta. |
…ple rules and backends * for an ingress with session affinity cookie, set the location as path on the cookie when unique * the previous behaviour ( cookie path=/ ) is preserved for ingresses with multiple rules for the same backend (locations not unique) added e2e tests for session affinity, setting path on sticky config added tests: * it should set the path to /something on the generated cookie * it should set the path to / on the generated cookie if there's more than one rule referring to the same backend
fix for #1930, make sessions sticky, for ingress with multiple rules …
…ple rules and backends * for an ingress with session affinity cookie, set the location as path on the cookie when unique * the previous behaviour ( cookie path=/ ) is preserved for ingresses with multiple rules for the same backend (locations not unique) added e2e tests for session affinity, setting path on sticky config added tests: * it should set the path to /something on the generated cookie * it should set the path to / on the generated cookie if there's more than one rule referring to the same backend
Is this a request for help? (If yes, you should use our troubleshooting guide and community support channels, see https://kubernetes.io/docs/tasks/debug-application-cluster/troubleshooting/.):
What keywords did you search in NGINX Ingress controller issues before filing this one? (If you have found any duplicates, you should instead reply there.):
Is this a BUG REPORT or FEATURE REQUEST? (choose one):
FEATURE REQUEST
NGINX Ingress controller version:0.9.0-beta.11
Kubernetes version (use
kubectl version
):1.5.2Environment:
uname -a
):Linux 3.10.0-693.11.6.el7.x86_64What happened:
my deploy yaml
I have 2 tomcat projects.
when visited "https://mooc1-k8s.chaoxing.com/test.jsp" i got k8s cookie, but i visited "https://mooc1-k8s.chaoxing.com/ananas/test.jsp" i got a new k8s cookie and
session missed.
like nginx-sticky:
https://bitbucket.org/nginx-goodies/nginx-sticky-module-ng
how to set path?
What you expected to happen:
k8s cookie should not changed.
How to reproduce it (as minimally and precisely as possible):
Anything else we need to know:
The text was updated successfully, but these errors were encountered: