External-dns: Multi target support and bugfixes Infoblox provider
Recently I cloned this repository and adjusted the Infoblox provider locally to work with multiple targets.
We're using this in a Rancher Kubernetes environment.
I would like to submit my work to merge it into the master branch.
H3rman8
All 12 comments
This is cool!
Is the usecase for split DNS setup? We would need quite the same.
Do you already prepared a PR?
jgrumboe
on 21 Feb 2020
/kind feature
seanmalloy
on 8 Mar 2020
It's not for split dns.
Fixed some bugs and get the provider working and being able to register multiple IP-addresses for services/ingresses, which is mostly the case when multiple pods are running on several nodes behind those services/ingresses.
I've got the code already tested and waiting to submit the pull request.
Just waiting for the approval to submit the pull request.
/kind bug
H3rman8
on 1 Apr 2020
Thanks for clarification on "not for split dns".
I also forked to repo and I'm working on Openshift route support together with Infoblox.
As you also mentioned bugfixes in the title, do you mean Infoblox bugfixes?
I would be interested in such but I couldn't find your fork to have a look.
jgrumboe
on 2 Apr 2020
Did run into same issues, within this infoblox provider (not the infoblox server itself).
Made the fork yesterday. Have to merge the adjustments into this fork and do same test.
I'll keep you posted.
H3rman8
on 3 Apr 2020
Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.
If this issue is safe to close now please do so with /close.
Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle stale
fejta-bot
on 2 Jul 2020
/remove-lifecycle stale
H3rman8
on 2 Jul 2020
Pull request is still to be approved.
H3rman8
on 16 Jul 2020
Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.
If this issue is safe to close now please do so with /close.
Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle stale
fejta-bot
on 14 Oct 2020
Pull request is still to be approved.
@H3rman8 is there an open pull request that would fix this bug?
seanmalloy
on 14 Oct 2020
@seanmalloy there is one and its still waiting to be approved.
https://github.com/kubernetes-sigs/external-dns/pull/1521
/remove-lifecycle stale
H3rman8
on 15 Oct 2020
Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.
If this issue is safe to close now please do so with /close.
Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle stale
fejta-bot
on 13 Jan 2021
Related issues
neilhwatson
路
4Comments
amalucelli
路
4Comments
placydo
路
5Comments
linki
路
4Comments
estahn
路
4Comments