Pega Session Affinity with AWS Application Load Balancer - JSESSIONID

[p-arikatla]

Describe the bug
When provisioning the helm chart with ingress.enabled: true, the helm chart template files provision the load balancer to use load balancer generated cookie. This is resulting in duplicating requestors id's and is affecting user functionality where session affinity is required. The request should route back to the same container where the request original from.

To Reproduce
Steps to reproduce the behavior.

Provisioned the helm charts using the values below:

ingress:
# Enter the domain name to access web nodes via a load balancer.
# e.g. web.mypega.example.com
enabled: false
ingressClassName: alb
annotations:
alb.ingress.kubernetes.io/target-type: ip

Expected behavior
Session Affinity - users request should route back to the same container in which it originated from. The user's requestor id shouldn't be duplicated across nodes.

Chart version
What version of the charts are you using? Have you made any customizations?

Version 3.25.1

The fix for this issue is adding the below annotation:

alb.ingress.kubernetes.io/target-group-attributes: load_balancing.algorithm.type=least_outstanding_requests,stickiness.enabled=true,stickiness.lb_cookie.duration_seconds=3720,stickiness.app_cookie.cookie_name=JSESSIONID,stickiness.type=app_cookie

Server (if applicable, please complete the following information):

• OS: Amazon Linux 2
• Environment: Amazon EKS
• Database: PostgreSQL