[EKS] [request]: Java application running on EKS cluster gave redis connection error after EKS upgrade and Amazon linux upgrade

### Community Note

**Which service(s) is this request for?**
This could be EKS

**Tell us about the problem you're trying to solve. What are you trying to do, and why is it hard?**
EKS upgrade 1.31 to 1.32
Amazon Linux 2 to Amazon Linux 2023
region: ap-south-1
Base Image used:
openjdk:jdk-11.0.3-stretch-build

We have a java application running on EKS cluster which connects to redis cluster running on EC2 to fetch data.
After upgrade from EKS 1.31 to 1.32 & movement from AL2 to AL2023, the application gave redis error.
we started getting issue on the application with new pods after EKS activity and even thou the release where freezed from longer time

**Are you currently working around this issue?**
For brute force immidiate fix :-
*we generate new build release and deployed.
*we have upgraded the java spring application redis version 3.2.0 to 3.2.6

Start by reproducing the Redis connection failure with the Java application after upgrading EKS from 1.31 to 1.32 and moving from Amazon Linux 2 to Amazon Linux 2023. Compare new and existing pods, the base image, and the Redis client versions 3.2.0 and 3.2.6; the work is done when the upgrade no longer causes the connection error or its cause is documented.

Written by the indexing model from the issue text.