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.

For more on sticky sessions, see here.
sticky sessions majorTom

Enable sticky sessions

To enable sticky sessions:

  1. Go to your values.yml file in your PaaS project.

  2. Set the following ingress annotations:

      enabled: true
      annotations: "nginx" 512m "letsencrypt-prod" "cookie" (1) "persistent" (2) "INGRESSCOOKIE" (3) "10" (4) {{ .Env.DEPLOYMENT }}-magnolia-error-page-svc "503"
        - host: {{ .Env.DEPLOYMENT }}
              - path: /
                instance: public
              - path: /author
                instance: author
    1 Set to cookie.
    2 Set to persistent.
    3 Put the INGRESSCOOKIE at
    4 Set to the time (in seconds) you want the cookie to persist. After this configured time, the cookie is deleted.




This widget lets you know where you are on the docs site.

You are currently perusing through the Magnolia PaaS docs.

Main doc sections

DX Core Headless PaaS Legacy Cloud Incubator modules