if alternate access two ingress paths, the session can't keep sticky

[hebo1982]

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.2

Environment:

• Cloud provider or hardware configuration:
• OS (e.g. from /etc/os-release): Linux version 3.10.0-693.11.6.el7.x86_64 (builder@kbuilder.dev.centos.org) (gcc version 4.8.5 20150623 (Red Hat 4.8.5-16) (GCC) )
• Kernel (e.g. uname -a):Linux 3.10.0-693.11.6.el7.x86_64
• Install tools:yum install
• Others:

What happened:
my deploy yaml

kind: Ingress
apiVersion: extensions/v1beta1
metadata:
  labels:
    app: mooc-pre
  name: mooc-pre
  namespace: pre
  annotations:
    kubernetes.io/ingress.class: "nginx"
    ingress.kubernetes.io/affinity: "cookie"
    ingress.kubernetes.io/session-cookie-name: "k8s"
    ingress.kubernetes.io/session-cookie-hash: "sha1"
spec:
  rules:
  - host: mooc1-k8s.chaoxing.com
    http:
      paths:
      - path: /ananas
        backend:
          serviceName: tomcat1
          servicePort: 8080
      - path: /
        backend:
          serviceName: tomcat2
          servicePort: 8080

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

 sticky [name=route] [domain=.foo.bar] [path=/] [expires=1h] 
       [hash=index|md5|sha1] [no_fallback] [secure] [httponly];

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:

[hebo1982]

---
kind: Ingress
apiVersion: extensions/v1beta1
metadata:
  labels:
    app: mooc-pre
  name: mooc-pre
  namespace: pre
  annotations:
    kubernetes.io/ingress.class: "nginx"
    ingress.kubernetes.io/affinity: "cookie"
    ingress.kubernetes.io/session-cookie-name: "k8s-2"
    ingress.kubernetes.io/session-cookie-hash: "sha1"
spec:
  rules:
  - host: mooc1-k8s.chaoxing.com
    http:
      paths:
      - path: /
        backend:
          serviceName: tomcat2
          servicePort: 8080
---
kind: Ingress
apiVersion: extensions/v1beta1
metadata:
  labels:
    app: html-editor-a-pre
  name: html-editor-a-pre
  namespace: pre
  annotations:
    kubernetes.io/ingress.class: "nginx"
    ingress.kubernetes.io/affinity: "cookie"
    ingress.kubernetes.io/session-cookie-name: "k8s-1"
    ingress.kubernetes.io/session-cookie-hash: "sha1"
spec:
  rules:
  - host: mooc1-k8s.chaoxing.com
    http:
      paths:
      - path: /ananas
        backend:
          serviceName: tomcat1
          servicePort: 8080

I solve that use two "ingress.kubernetes.io/session-cookie-name: k8s-X"

[Atoms]

yes, have same problem, and i found where the problem is in code:

ingress-nginx/rootfs/etc/nginx/template/nginx.tmpl

Line 319 in a30bf21

sticky hash={{ $upstream.SessionAffinity.CookieSessionAffinity.Hash }} name={{ $upstream.SessionAffinity.CookieSessionAffinity.Name }} httponly;

it does not use all parameters from nginx-sticky-module-ng

[fejta-bot]

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle stale

[fejta-bot]

Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle rotten
/remove-lifecycle stale