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

No MaxResults for Infoblox Provider #221

Closed
SelisNic opened this issue Jul 24, 2024 · 3 comments
Closed

No MaxResults for Infoblox Provider #221

SelisNic opened this issue Jul 24, 2024 · 3 comments

Comments

@SelisNic
Copy link

On the regular External-DNS helm chart there is an option to provide a maxResults setting at the Infoblox Provider.
Is it possible to provide it in the External-DNS Operator as well? We need this setting because we have more than 1000 objects in our Infoblox domain filter. (kubernetes-sigs/external-dns#953). For now we are getting this error:

"Error": "AdmConProtoError: Result set too large (> 1000)"

@philipsabri
Copy link

We are having the same issue and are raising a ticket on redhat openshift support.

@candita
Copy link

candita commented Aug 28, 2024

Jira ticket raised. Closing issue.
/close

@openshift-ci openshift-ci bot closed this as completed Aug 28, 2024
Copy link
Contributor

openshift-ci bot commented Aug 28, 2024

@candita: Closing this issue.

In response to this:

Jira ticket raised. Closing issue.
/close

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.

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