Skip to content
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 IPAM range #137

Closed
UltraInstinct14 opened this issue Apr 25, 2024 · 3 comments
Closed

Support for IPAM range #137

UltraInstinct14 opened this issue Apr 25, 2024 · 3 comments

Comments

@UltraInstinct14
Copy link
Collaborator

Currently kube-loxilb configuration needs IPAM to be specified as a prefix. For more user-friendly configuration, it would be great if kube-loxilb can support IPAM range as configuration. For example : - --externalCIDR=192.168.80.200-192.168.80.205

@6547709
Copy link

6547709 commented Nov 18, 2024

I recently encountered this requirement. Since there are not many available IPs left in the subnet, when will it be supported?

@TrekkieCoder
Copy link
Collaborator

@6547709 This is set to be supported in ~ 2 weeks time frame from now.

TrekkieCoder added a commit to TrekkieCoder/loxilib that referenced this issue Nov 22, 2024
UltraInstinct14 added a commit to loxilb-io/loxilib that referenced this issue Nov 22, 2024
UltraInstinct14 added a commit that referenced this issue Nov 23, 2024
gh-137 Support for ip-ranges  in IPAM in addition to cidr
@TrekkieCoder
Copy link
Collaborator

The IPAMs can be specified as range now - --externalCIDR=192.168.80.200-192.168.80.205 in kube-loxilb args or in CRD.

TrekkieCoder added a commit that referenced this issue Nov 23, 2024
TrekkieCoder added a commit that referenced this issue Nov 23, 2024
UltraInstinct14 added a commit that referenced this issue Nov 23, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants