Sticky sessions

Sticky sessions, or session persistence, is when you instruct the load balancer to remain linked to a specific node (server) to avoid losing the session data if the request goes to the other server. Essentially, you send the request from a given IP to the delivery server, but continue to send follow-up requests to the same server until the session expires. Session persistence is needed when the project has transactions or required data in the session.

Sticky sessions are typically used in situations where you have some data in the session and the sessions are not replicated between servers, but you also need to ensure that the data doesn’t get lost.

Enable sticky sessions

Set sticky sessions on the MgnlIngress. Leave ingress.enabled off in values.yml.

Field names are in Map UI fields to manifest.

1. Open the Ingress in the Cockpit, or open the MgnlIngress manifest in your pipeline.
2. Set nginxOptions.stickySession as in the example below.

nginxOptions:
  stickySession:
    enabled: true <1>
    cookieName: "INGRESSCOOKIE" <2>
    cookieMaxAgeInSecond: 3600 <3>

Sticky session. Set enabled to true for cookie-based session affinity.

Name of the affinity cookie. If you use a cookie-based redirect server, this name must be different from that server’s cookie name.

How long the cookie lasts, in seconds. After this time, the cookie is deleted.