istio-gateway is not exposing option to select AZs for EKS

[gustavosr98]

Bug Description

When deploying Istio gateway as a LoadBalancer on AWS EKS it will auto create a Classic AWS Load Balancer in a random AZ

It will select only one Availability Zone within the region
However, EKS k8s worker nodes might no be on that AZ, thus the LB will not be able to have communication with the k8s workers

Additionally, the LB needs to be added to all AZs where there is a k8s worker

Thus, I would suggest either to set the LB in all AZs by default or expose an option on the charm to select the AZs where the LB should be created

This can be done through the manifest.yaml when creating the kubernetes service for it
https://kubernetes-sigs.github.io/aws-load-balancer-controller/v2.2/guide/service/annotations/

To Reproduce

juju deploy --trust --debug istio-gateway
--channel=1.16/stable
--config kind=ingress
--config gateway_service_type=LoadBalancer

Environment

AWS EKS
Juju 2.9.45
Charm channel: 1.16/stable
Charm revision: 663

Relevant log output

n/a

Additional context

Conversation about it on Charmhub chat / Juju channel
https://chat.charmhub.io/charmhub/pl/1g8iz391hbdnjnoxhsgp6c3pih

Workaround
Manually through AWS GUI:
Load Balancers / Detail / Network mappings / Edit subnet / Enable the required AZs

[orfeas-k]

This is related to #66.

[syncronize-issues-to-jira]

Thank you for reporting us your feedback!

The internal ticket has been created: https://warthogs.atlassian.net/browse/KF-5275.

This message was autogenerated