search

kubernetes-sigs / external-dns

Configure external DNS servers (AWS Route53, Google CloudDNS and others) for Kubernetes Ingresses and Services
Apache License 2.0
7.7k stars 2.56k forks source link

Infoblox provider fails with: Result set too large #784

Closed dvob closed 5 years ago

dvob commented 5 years ago

The Infoblox provider does not work if you have more than 1000 records in a zone and it's not clear which zone causes the problem.

To avoid this problem it should be possible to pass the _max_results query parameter with the API calls to Infoblox. This is not possible with the current infoblox go client (infobloxopen/infoblox-go-client#73).

Until this is fixed we could at least show which zone causes the problem that one can change the --domain-filter or --zone-id-filter accordingly.

gregsidelinger commented 5 years ago

I'm running into this issue with some of the larger zones we have. The Infoblox API does support pagination to help get around this without having to set _max_results to very large numbers. However I'm not sure if the infoblox-go-client supports it.