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
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): BUG REPORT
NGINX Ingress controller version: 0.19.0
Kubernetes version (use kubectl version): v1.10.7
Environment:
Cloud provider or hardware configuration: AWS
OS (e.g. from /etc/os-release):
Kernel (e.g. uname -a):
Install tools:
Others:
What happened:
We have two ingresses, one with sticky session annotations, one without:
Both curl foo.bar.com/common/v1 and curl foo.bar.com/common/v1/real-time show Set-Cookie: sticky=3bda432b6d65261863c79208ea1c156652e905a7; Domain=foo.bar.com; Path=/; HttpOnly
What you expected to happen:
Only curl foo.bar.com/common/v1/real-time should apply the sticky cookie.
How to reproduce it (as minimally and precisely as possible):
Anything else we need to know:
Looks like stick annotations are per service rather then per ingress.
The text was updated successfully, but these errors were encountered:
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/test-infra repository.
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): BUG REPORT
NGINX Ingress controller version: 0.19.0
Kubernetes version (use
kubectl version
): v1.10.7Environment:
uname -a
):What happened:
We have two ingresses, one with sticky session annotations, one without:
Both
curl foo.bar.com/common/v1
andcurl foo.bar.com/common/v1/real-time
showSet-Cookie: sticky=3bda432b6d65261863c79208ea1c156652e905a7; Domain=foo.bar.com; Path=/; HttpOnly
What you expected to happen:
Only
curl foo.bar.com/common/v1/real-time
should apply the sticky cookie.How to reproduce it (as minimally and precisely as possible):
Anything else we need to know:
Looks like stick annotations are per service rather then per ingress.
The text was updated successfully, but these errors were encountered: