btzq commented on issue #9506: URL: https://github.com/apache/cloudstack/issues/9506#issuecomment-2326307774
Hey @rohityadavcloud , im refering to the built in Load Balancing feature in the Cloudstack Virtual Router.  Right now, when we create a Load Balance (or Load Balancer via an AutoscaleGroup), Cloudstack requires a Public IP to be associated to the LB to work. This is done by doing the following steps: - Go to VPC > Public IP Addresses > Acquire New IP - Go to Public IP Adresses Menu > Select Public IP > Create Load Balance Rule - Create Autoscale Group > Enter Mandatory Info > Select Load Balancer As a result, it is required for users to create a LB (and Autoscale Group) with a Public IP. In our case, we have the following scenarios: 1. Internet/LeasedLine -> ASG LB (Service 1) -> Database 2.Internet/LeasedLine -> ASG LB (Service 1) -> ASG LB (Service 2) -> Database 3.Internet/LeasedLine -> ASG LB (Service 1) -> Private GW to another VPC within same zone -> ASG LB (Service 2) -> Database In scenarios 2 and 3, there is no need for the LB to use a Public IP, because they are only meant to be receiving traffic from other VMs via LAN. Only the LB for (Service 1) requires a Public IP. By enhancing Cloudstack to allow the creation of LB using a Private IP achieve 2 things: - Save Cost by Reducing the number of Public IPs required - Better security, because LBs that do not need to talk to the internet, are not exposed to the internet. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
