-
Notifications
You must be signed in to change notification settings - Fork 2.6k
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
Infoblox - Correct GetObject query #2890
Infoblox - Correct GetObject query #2890
Conversation
|
/assign @njuettner |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
/lgtm
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: njuettner, skalpin The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
Can we get a release for this fix and a huge warning on all releases before this fix? |
+1, we need a hotfix release for this. Completely messed up our infoblox. |
@seanmalloy @njuettner @Raffo Do you all have any ETA for when a new release will be created with this fix? |
@zreigz Do you know when the next release will be? This fix is sorely needed. As it stands, we can't upgrade external-dns due to this issue. |
sorry, I am the wrong person for this |
Ah apologies. I saw your name in the commits. Thanks for your other work! :) |
With respect to them having a huge bug for the Infoblox provider. See kubernetes-sigs#2890
Description
The ibclient.GetObject will return all the objects associated with the query. This is an issue when external-dns has identified 1 record to remove. The object being created retrieves many more records than expected and so external-dns will delete all the matching records.
This change adds one "name" filter to the query parameters so that only the expected record is removed from infoblox
Checklist