-
Notifications
You must be signed in to change notification settings - Fork 123
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Support for AWS multi-AZ #681
Comments
ElasticIP needs to be reassociated to active EC2 instance. For fullNAT mode to work, a private CIDR needs to be associated with loxi instances. The privateCIDR also needs to migrate to active VPC. |
Overall pattern is as follows -
The following is an example HA configuration. Kindly change the instance's IP and subnet settings as per need. VPC CIDR: 192.168.0.0/16 Setting up kube-loxilb
In loxiURL, specify loxilb 1 & 2 instance's IP. Setting up loxilb instances
In --cloudcidrblock option, specify the CIDR of your private subnet.
|
Multi-VPC support is yet to be validated hence currently limited to multi-AZ in same VPC !! |
Is your feature request related to a problem? Please describe.
If loxilb runs in two instances with each instance in a different VPC or AZ, currently the same VIP for communication can't be maintained.
Describe the solution you'd like
loxilb instances should be able to run in different VPCs/AZ with the same VIP CIDR
Describe alternatives you've considered
N/A
Additional context
There is high-level AWS design pattern how this could be achieved.
The text was updated successfully, but these errors were encountered: