You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Apr 18, 2019. It is now read-only.
Any time a zone has more than 1000 records the controller blows up and is unable to process requests for that zone. This has to do with the infoblox go library not supporting pagination and infloblox default of returning an error when more than 1000 results are returned.
A way to filter the DNS zones you care about would also be helpful as it took over 2 hours to scan the few thousand zones we have. I had to hand add the _max_results flag to your code to get it so "work" with the large number of zones we have. I only care to have this controller manage a few of them.
Orchestration Name and Version
kubernetes 1.11
Controller Version
v0.1.0
IPAM System and Version
Infoblox 2.7 API
The text was updated successfully, but these errors were encountered:
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Description
Any time a zone has more than 1000 records the controller blows up and is unable to process requests for that zone. This has to do with the infoblox go library not supporting pagination and infloblox default of returning an error when more than 1000 results are returned.
A way to filter the DNS zones you care about would also be helpful as it took over 2 hours to scan the few thousand zones we have. I had to hand add the _max_results flag to your code to get it so "work" with the large number of zones we have. I only care to have this controller manage a few of them.
Orchestration Name and Version
kubernetes 1.11
Controller Version
v0.1.0
IPAM System and Version
Infoblox 2.7 API
The text was updated successfully, but these errors were encountered: