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
IP ranges no longer work #2221
Comments
I'll provide logs later if required, but can't currently access them since i wont destry our production system again. |
I confirm issue. IP range wasn't working for me either. CIDR My set-up: |
I would like to work on it. |
thanks! assigned |
You just need to modify the "autoAssign" field, and this will work for you.
|
i don't want to enable auto assign. I've now converted all ip ranges to use cidr format. |
Okay, I will check it and update here. @viceice |
Hi, I was able to reproduce the bug on v0.13.12 but not on main, which makes me think this was probably fixed in some commit in between (I'm not totally sure which one). I'll modify the existing tests to include the autoAssign:false case so we won't regress again as I can see it is missing. thanks :) @viceice |
thanks, when can we expect a new release? |
sometime next week (I started preparing the rel notes #2261) . Please make sure you don't see the problem deploying from main if you cna |
Closing this issue based on the above discussion. @viceice feel free to reopen if 0.14.3 (or main) do not work. |
MetalLB Version
0.13.12
Deployment method
Charts
Main CNI
calico
Kubernetes Version
1.27.8
Cluster Distribution
k3s
Describe the bug
IP ranges no longer work on IP pools
To Reproduce
Apply this pool an try to use
172.30.2.70
from that pool and get the not allowed error on the service.Expected Behavior
Ranges should work like they did some versions before.
Additional Context
Workaround: use cidr ips
I've read and agree with the following
I've read and agree with the following
The text was updated successfully, but these errors were encountered: