DevFW-CICD/ingress-nginx-helm
16
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

Adds a new situation in affinity config example

Browse source
This commit is contained in:
Ricardo Pchevuzinske Katz 2017-02-16 08:40:35 -02:00
parent 59dd5556bd
commit 93d5065da1
1 changed files with 3 additions and 0 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

3
examples/affinity/cookie/nginx/README.md
View file

@ -72,3 +72,6 @@ If the backend pool grows up NGINX will keep sending the requests through the sa
When the backend server is removed, the requests are then re-routed to another upstream server and NGINX creates a new cookie, as the previous hash became invalid. When the backend server is removed, the requests are then re-routed to another upstream server and NGINX creates a new cookie, as the previous hash became invalid.
When you have more than one Ingress Object pointing to the same Service, but one containing affinity configuration and other don't, the first created Ingress will be used.
This means that you can face the situation that you've configured Session Affinity in one Ingress and it doesn't reflects in NGINX configuration, because there is another Ingress Object pointing to the same service that doesn't configure this.