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

Infoblox update #58

Merged
merged 3 commits into from
Mar 9, 2020
Merged

Infoblox update #58

merged 3 commits into from
Mar 9, 2020

Conversation

ytsarev
Copy link
Member

@ytsarev ytsarev commented Mar 6, 2020

It's a thousand of unpredictable from the vendor. With capital V

ytsarev added 3 commits March 4, 2020 14:49
* In case of Infoblox -ns entries are automatically and indirectly
  created by zone delegation api call
* Because of that the external-dns does not really 'own' them
* Thus, we need to move splitbrain TXT timestamping to a separate
  DNS name
* It appeared that API kick of ZoneDelegated makes Infoblox
  to create required NS and A records automatically
* TXT splitbrain DNSEndpoint creation would make sense
  but it appeared to be silently not working in e2e tests
* So we are getting rid of dedicated external-dns-infoblox deployment
  completely simplifying the setup
* TXT splitbrain are about to be created with ibclient based API kick
* Use modified ibclient with TXT management capabilities
@ytsarev ytsarev requested a review from donovanmuller March 8, 2020 13:42
Copy link
Contributor

@donovanmuller donovanmuller left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

If I'm reading this correctly, does this mean a more direct integration with Infoblox, which now doesn't leverage External DNS's Infoblox implementation?

If so, what does that mean for future external DNS integrations like Route 53 etc.?

@ytsarev
Copy link
Member Author

ytsarev commented Mar 8, 2020

@donovanmuller yeah, initially I was trying to make it as generic as possible.
But it crashed over two points:

  • NS and associated A records are getting created automatically by infoblox from ZoneDelegaged kick
  • TXT record just does not work with externaldns-infoblox

So I decided to get rid of externaldns-infoblox completely and make direct api kick with ibclient for TXT record ( and it works reliably) .

Looks like for every edgeDNS we will have to treat special API call and it is unfortunately unavoidable. Obviously , happy to discuss the thing deeper

@donovanmuller donovanmuller merged commit 268a54a into master Mar 9, 2020
@ytsarev ytsarev deleted the infoblox-update branch August 2, 2020 10:21
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

Successfully merging this pull request may close these issues.

2 participants