Skip to content
This repository has been archived by the owner on Apr 17, 2019. It is now read-only.

[nginx-ingress-controller] Feature request: enable session stickiness per-ingress #1807

Closed
emmanuel opened this issue Sep 29, 2016 · 7 comments
Labels
lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed.

Comments

@emmanuel
Copy link

We are currently using the ingress-global session stickiness, but have apps with different needs and would like to be able to utilize stickiness on specific ingresses. Based on the other annotation-based configurations that are available per-ingress, it looks like this is not a huge change, since the capability to configure upstreams per-ingress is already present. WDYT?

@aledbf
Copy link
Contributor

aledbf commented Sep 29, 2016

@emmanuel already present in the TODO List :)

@emmanuel
Copy link
Author

Wahoo! Thanks @aledbf. Man, you are fast!

@Jno21
Copy link

Jno21 commented Jan 12, 2017

Hello, could we have an update on this feature ? :)

Thanks !

@aledbf
Copy link
Contributor

aledbf commented Feb 22, 2017

@emmanuel @Jno21 please check new release here where the feature was introduced.

@fejta-bot
Copy link

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.

Prevent issues from auto-closing with an /lifecycle frozen comment.

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

@k8s-ci-robot k8s-ci-robot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Dec 21, 2017
@fejta-bot
Copy link

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

@k8s-ci-robot k8s-ci-robot added lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed. and removed lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. labels Jan 20, 2018
@fejta-bot
Copy link

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.

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

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed.
Projects
None yet
Development

No branches or pull requests

5 participants