Setting custom affinity cookie name using nginx ingress controller in kubernetes for Jira
Platform Notice: Data Center Only - This article only applies to Atlassian products on the Data Center platform.
Note that this KB was created for the Data Center version of the product. Data Center KBs for non-Data-Center-specific features may also work for Server versions of the product, however they have not been tested. Support for Server* products ended on February 15th 2024. If you are running a Server product, you can visit the Atlassian Server end of support announcement to review your migration options.
*Except Fisheye and Crucible
Summary
You might need to customize the session cookie name used by the ingress controller for their Jira deployments running on Kubernetes via Atlassian DC helm charts. The default name of the cookie is INGRESSCOOKIE.
Environment
Kubernetes
Atlassian DC Helm Charts
Solution
Please use the following annotation in the values yaml file used to deploy Jira.
1
2
3
4
ingress:
...
annotations:
nginx.ingress.kubernetes.io/session-cookie-name : "CUSTOMCOOKIE"Warning
Please do not use JSESSIONID for the cookie name for the ingress controller. It is used by Jira for the user session and Jira will reset the value if the cookie is not set by itself. This will cause the nginx ingress controller and Jira to reset the cookie.
Was this helpful?