Percona Everest needs option to specify creation of Internet-facing or internal load-balancer

[telderfts]

Currently when creating a database cluster in Percona Everest you can expose the database to traffic outside of the VPC. Right now it appears that Percona Everest simply changes the service type and adds an annotation to be an NLB. There needs to be an option for the Load-balancer to be internet-facing, which is the default, or Internal facing which is more secure for those with a cloud environment, especially in AWS. This should be as easy as including an annotation that specifies whether or not it is internal and either a drop down or check-box when making the database externally accessible.

[telderfts]

To add more context, for instance in AWS, if you want to use an internal load balancer you have to leave external access turned off and then manually change the mysql-haproxy service to LoadBalancer with the annotations for Internal load balancing which seems to defeat the entire purpose of allowing external access. Most users don't want their DB's open to public traffic where they are paying for data transfer costs if the app connecting to the DB is located in a different VPC.