[EKS] [request]: Reinstaling istio helm chart in EKS recreates a new ALB with a different FQDN

### Community Note

* Please vote on this issue by adding a 👍 [reaction](https://blog.github.com/2016-03-10-add-reactions-to-pull-requests-issues-and-comments/) to the original issue to help the community and maintainers prioritize this request
* Please do not leave "+1" or "me too" comments, they generate extra noise for issue followers and do not help prioritize the request
* If you are interested in working on this issue or have submitted a pull request, please leave a comment

**Tell us about your request**
What do you want us to build?
Persistence of ALB FQDN while reinstalling istio operator helm chart in AWS EKS

**Which service(s) is this request for?**
This could be Fargate, ECS, EKS, ECR
EKS
**Tell us about the problem you're trying to solve. What are you trying to do, and why is it hard?**
We are using Istio operator (installed with helm chart ) to create ingress for EKS applications. This Istio creates ALB in AWS as the load balancer . We were facing some issue while upgrading the istio helm chart. So we removed and reinstalled the istio helm chart but this time it recreates a new ALB with a new FQDN.

We need a solution so that if we remove and reinstall the istio helm chart , it should use the same ALB (same old FQDN) which was attached with earlier istio.

**Are you currently working around this issue?**
How are you currently solving this problem?
NA
**Additional context**
Anything else we should know?
NA
**Attachments**
If you think you might have additional information that you'd like to include via an attachment, please do - we'll take a look. (Remember to remove any personally-identifiable information.)

The issue names EKS, the Istio operator Helm chart, and the AWS ALB, but no repository files, tests, or entry points. Start by reproducing the uninstall-and-reinstall flow and reviewing how the chart provisions the ALB; done means reinstalling the chart preserves the original ALB and FQDN.

Written by the indexing model from the issue text.